ID: 1165
Title: Fixed exception in service discovery of logwatch event console forwarding checks
Component: WATO
Level: 1
Class: Bug Fix
Version: 1.2.5i7
When a service "logwatch.ec" (event console forwarding) is found via service discovery
and the check parameters are displayed in the table, an exception occured, because
WATO could not interpret the inventorized parameters correctly.
ID: 1478
Title: kernel.util, statgrab_cpu: fix computation of utilization
Component: Checks & Agents
Level: 1
Class: Bug Fix
Version: 1.2.5i7
This was broken due to a recent code restructuration.
ID: 1430
Title: Clone group: Now displays correct alias name of cloned group
Component: WATO
Level: 1
Class: Bug Fix
Version: 1.2.5i6
This applies to contact-, host- and servicegroups.
ID: 1443
Title: ups_socomec_outphase: New check for monitoring the out phases of Socomec UPSs
Component: Checks & Agents
Level: 1
Class: New Feature
Version: 1.2.5i6
ID: 1196
Title: apache_status: Added timeout
Component: Checks & Agents
Level: 1
Class: New Feature
Version: 1.2.5i6
The apache_status plugin now has a timeout for the urlopen operation.
ID: 1429
Title: Disabled snmp checktypes are now sorted out before Check_MK contacts the snmp host
Component: Core & Setup
Level: 2
Class: Bug Fix
Version: 1.2.5i6
Behaviour in the previous version: If a snmp host should be inventorized it was checked
with the full palette of all available snmp inventory functions. The filtering of unwanted checktypes
was done afterwards. This caused needless snmp queries towards the snmp host.
The filtering of unwanted checktypes is now done before the snmp host is contacted.
Note: This only applies to the WATO rule <i>Disabled checktypes</i> respectively the parameters
<tt>ignored_checktypes</tt> and <tt>ignored_checks</tt>, but not to <i>Disabled services</i>.
The latter one matches to service descriptions which are the result of a successful inventory.
ID: 1428
Title: Web-API: now able to add cluster hosts
Component: WATO
Level: 1
Class: New Feature
Version: 1.2.5i6
Its quite easy to accomplish. On your add host telegram simply add
the new key <tt>{ ".nodes" = ["nodename1", "nodename2"] }</tt>.
Please note that the existance of the nodes is not verified.
So you might get an invalid host configuration and being unable
to activate the changes.