ID: 0973
Title: Renaming of hosts via WATO
Component: WATO
Level: 2
Class: New Feature
Version: 1.2.5i3
WATO has now a new function <i>Rename Host</i>. You will find a button with that name
in the Properties of a host. It allows a renaming of an existing host. Before you
can use that feature you need to have all changes activated, so nothing is pending.
Renaming a host is a complex precedure that will not only rename the host in WATO,
but also in:
<ul>
<li>all rules from <i>Host & Service Parameters</i></li>
<li>cluster's node definitions</li>
<li>a host's parent definitions</li>
<li>Business Intelligence rules</li>
<li>notification rules (both rule based and flexible notifications)</li>
<li>internal Check_MK data like caches and performance counters</li>
<li>auto-disovered services of the host</li>
<li>logfile information of logwatch plugin</li>
<li>stored SNMP walks</li>
<li>RR databases with performance data</li>
<li>RRD updates in journal of RRD Cache</li>
<li>spool files of PNP4Nagios</li>
<li>NagVis maps</li>
<li>monitoring history entries (events and availability)</li>
<li>the current monitoring state (including ackowledgements and downtimes)</li>
</ul>
Please note that renaming of a host involves a temporary stop of the monitoring
core. This is neccessary in order to avoid situation where the old and the new
name of a host is being used at the same time.
ID: 2022
Title: SNMP: Fixed handling of backslashes in SNMP data
Component: Checks & Agents
Level: 2
Class: Bug Fix
Version: 1.2.7i1
Some checks like the hr_fs checks e.g. create services with
backslashes in the service descriptions when monitoring
windows filesystems. Those services were named "Filesystem c:\\..."
for example, which was using a double backslash which is wrong.
This behaviour has now been changed to just use a single slash.
With this change your services will be reported as UNKNOWN when
you have such services with double backslashes in their names.
You will then need to rediscover the services to get them with
just a single slash. If you like to keep the performance graph
history, you will need to migrate them on your own.
ID: 1947
Title: agent_ucs_bladecenter: Monitors UCS Bladecenter via Web-API
Component: Checks & Agents
Level: 2
Class: New Feature
Version: 1.2.7i1
The new agent_ucs_bladecenter allows you to collect data from a
UCS Bladecenter via its web-API.
The following checks are currently supported
<table>
<tr><th>Check</th><th>Description</th></tr>
<tr><td>ucs_bladecenter_fans</td><td>Operate status of fans</td></tr>
<tr><td>ucs_bladecenter_fans.temp</td><td>Temperature at fans sensors</td></tr>
<tr><td>ucs_bladecenter_fans.temp</td><td>Temperature at chassis sensors</td></tr>
<tr><td>ucs_bladecenter_psu</td><td>Chassis voltage levels</td></tr>
<tr><td>ucs_bladecenter_psu.switch_power</td><td>Switch Voltage, Current and Power.</td></tr>
<tr><td>ucs_bladecenter_if</td><td>Traffic and bandwidth for Ethernet, Interconnect and Fibrechannel Ports.
Automatically groups portchannel interfaces.</td></tr>
</table>
Note: Portchannels for fibrechannel interfaces are not supported yet. It will be available soon.
ID: 1977
Title: Dramatically reduced size of Check_MK check helper processes
Component: Core & Setup
Level: 2
Class: Bug Fix
Version: 1.2.7i1
Optimized the memory footprint of the Check_MK check helper processes
which are used when using the CMC.
ID: 1860
Title: df and other filesystem checks: process total fs size as perfdata
Component: Checks & Agents
Level: 2
Class: New Feature
Version: 1.2.7i1
Since the total size of a filesystem may change we store the total size
as additional performance data and plot it with rrdtools like the used space.
As a consequence another rrd database file is created for every filesystem,
and slightly more disk space will be used for the rrd data of your site.
ID: 1973
Title: Added intelligent host and service type icons to default views
Component: Multisite
Level: 2
Class: New Feature
Version: 1.2.7i1
The default list views of hosts and services show a new column, the
type icon, by default now.
The rendered icon is some kind of intelligent icon. It tries to detect
which icon has to be shown for each host or service. This is done
automatically based on the available information, for example which
services are configured for a host or what is the name of a service.
The currently implemented auto detection is far from being complete.
It only contains some examples to show the new possibilites. This can
be extended using icon plugins. For details take a look at the default
<tt>plugins/icons/builtin.py</tt> code.
If you like to change / override the icon by hand, you can configure the
already existing rulesets "Icon image for hosts in status GUI" and
"Icon image for services in status GUI".
You can choose from the PNG icons available in <tt>htdocs/images/icons</tt>.
If you use OMD, the default files are located in <tt>share/check_mk/web/htdocs/images/icons</tt>.
You can place your own files in <tt>local/share/check_mk/web/htdocs/images/icons</tt>.