ID: 0975
Title: esx_vsphere_vm.guest_tools: renamed check (formerly esx_vsphere_vm.guestTools)
Component: Checks & Agents
Level: 1
Class: Incompatible Change
Version: 1.2.5i3
Due to a inconstent naming we had to rename the check {esx_vsphere_vm.guestTools} into {esx_vsphere_vm.guest_tools}.
Please reinventorize the affected hosts in order to switch over to the new plugin.
ID: 0957
Title: fast_lta_silent_cubes.capacity: New check for Total Capacity over all Silent Cubes on FAST LTA Storage Systems
Component: Checks & Agents
Level: 2
Class: New Feature
Version: 1.2.5i3
ID: 0974
Title: New notification plugin for ASCII emails
Component: Notifications
Level: 2
Class: New Feature
Version: 1.2.5i3
There is now a new notification script for ASCII emails. Just like the
HTML email template it is configurable with WATO via host rules and
notification rules. You can configure several header fields as well
as the exact body content. It also supports bulk notifications.
This new script obsoletes the plain builtin ASCII emails that are
now called <i>ASCII email (legacy)</i>.
ID: 0956
Title: fast_lta_headunit.status, fast_lta_headunit.replication: New checks for FAST LTA Storage Systems
Component: Checks & Agents
Level: 2
Class: New Feature
Version: 1.2.5i3
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: 0918
Title: notification: fixed exception when sending notifications as sms / ascii mail
Component: Notifications
Level: 2
Class: Bug Fix
Version: 1.2.5i3
Flexible notification plugins with configurable parameters did not work if
the parameters were configured as list of strings.
This exception happened on notications send by ASCII mails and sms.
ID: 0162
Title: if_brocade: New if64 Check version for Brocade VDX Switches
Component: Checks & Agents
Level: 2
Class: Incompatible Change
Version: 1.2.5i3
This check does the same like the normal if64 check. The only difference is that ifName is used instead of ifDescription.
You may want to do a reinventory on broace switches, because otherwise the "Check_MK Inventory" check (if used) will trigger warning state
cause of unchecked services.
ID: 0955
Title: zfs_arc_cache, zfs_arc_cache.l2: New Checks for Hit Ratios and Sizes of ZFS
Component: Checks & Agents
Level: 2
Class: New Feature
Version: 1.2.5i3