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: 1409
Title: Extended Check_MK-API: check function may return None
Component: Checks & Agents
Level: 2
Class: New Feature
Version: 1.2.5i6
A check function may now return <tt>None</tt> (or simply end without
returning anything). This will no longer create an exception but return
state <tt>UNKNOWN</tt> and - depending on the type of the check -
one of the following outputs:
<tt>Item not found in SNMP data</tt>
<tt>Item not found in agent output</tt>
This means that for the typical check that loops through the agent
output looking for its item now does not need to manually do a
C+:
return 3, "Something not found in agent output"
C-:
anymore. This is now the default case. This has several advantages:
<ul>
<li>You save some code in the check implementation.</li>
<li>The output of the various checks is unified.</li>
<li>A future Check_MK version can easily have a rule for changing the state
in such cases from UNKNOWN to WARN or CRIT.</li>
</ul>
ID: 1120
Title: Multisite filters Host/Service Contactgroup: Fixed livestatus exception
Component: Multisite
Level: 2
Class: Bug Fix
Version: 1.2.5i6
The multisite filters <tt>Host Contactgroups</tt> and <tt>Service Contactgroups</tt> were
not working because of an incorrect livestatus filter formatting.
This resulted in an livestatus exception every time any of these filters were actively used.
ID: 1408
Title: mknotifyd now really reads all configuration files below mknotifyd.d
Component: Notifications
Level: 2
Class: Bug Fix
Version: 1.2.5i6
Previously the notification spooler daemon <tt>mknotifyd</tt> just read the
single file <tt>etc/check_mk/mknotifyd.d/wato/global.mk</tt>. Now it reads
all files below <tt>etc/check_mk/mknotifyd.d</tt> - just as one would
expect. Note: there is still no <tt>etc/check_mk/mknotifyd.mk</tt> file.
ID: 1406
Title: Assume PEND in count_ok aggregations if all nodes are PEND
Component: BI
Level: 2
Class: New Feature
Version: 1.2.5i6
If you are using the BI aggregation function <tt>count_ok</tt> then nodes
with the state <tt>PEND</tt> (which essentially means unmonitored or not
present) are handled differently from now.
If <b>all</b> nodes are pending then the total state will also be pending.
If just some of the nodes are pending then they will not taken into account.
This is especially imported when doing availability computations on
BI aggregates.
ID: 1405
Title: Checkbox for settings downtimes on the hosts of the selected services
Component: Multisite
Level: 2
Class: New Feature
Version: 1.2.5i6
In the Multisite command box for setting downtimes on services there is now
a new checkbox called <i>Schedule downtimes on the affected hosts instead
of their services</i>. When you check this then the scheduled downtimes
are set on the hosts of the selected services rather then on the services
themselves. Note: When a host is in scheduled downtime then all its services
are considered to be in a scheduled downtime, as well. There is no need to
set a downtime on these.
ID: 1117
Title: agent_vsphere: now able to query license information from esx system
Component: Checks & Agents
Level: 2
Class: New Feature
Version: 1.2.5i6
The agent_vsphere is now able to get the license usage from the LicenseManager instance.
Upon inventory each license will lead to an own check name esx_licenses.
The check parameters (absolute used, percentage used, all used) can be configured via the WATO rule
<tt>Number of used VMware licenses</tt>
ID: 1403
Title: kernel.util: allow levels for the total CPU utilization
Component: Checks & Agents
Level: 2
Class: New Feature
Version: 1.2.5i6
The CPU utilization check for Linux only allowed to set levels for the disk
wait percentage. The parameters have been converted to a dictionary and
now allow to set levels on the total CPU utilization as well.
Please note: if you have defined the variable {kernel_util_default_levels} in
your {main.mk}, then you need to convert this to a dictionary - otherwise it
will be ignored. Instead of
F+:main.mk
kernel_util_default_levels = (10, 20)
F-:
... please now write...:
F+:main.mk
kernel_util_default_levels = { "iowait" : (10, 20) }
F-:
Users of WATO are not affected by this and do not need to change anything.