ID: 1863
Title: cisco_power: fix for cases with a slash in the device description of a power supply
Component: Checks & Agents
Level: 1
Class: Bug Fix
Version: 1.2.7i1
Power Supplies with a slash in the device description were added in service discovery,
but could not be found when carrying out the check. This problem has been fixed.
In addition, when you have power supplies which have a service description
containing the ID of the power supply at the end like "<power supply
name>/<ID>", i.e. with a SLASH, you have to redo the service discovery
and the service description will then contain the ID added with a blank
instead, i.e. "<power supply name> <ID>". This is a rare case only relevant
for versions of cisco_power younger than 2015/01/30, and only if you have
non-unique power supply names with trailing digits in the name.
ID: 2040
Title: Allow commands for setting downtimes and acknowledging on BI aggregates
Component: Multisite
Level: 1
Class: New Feature
Version: 1.2.7i1
The commands for scheduling downtimes and for acknowledging problems and removing
acknowledgements now can be done on BI aggregates. This is the same as performing
these commands on all hosts and services that are contained in the selected
BI aggregates. Note: removing downtimes currently does not work that way.
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: 1223
Title: Fixed manual configuration of ntp peer check
Component: WATO
Level: 1
Class: Bug Fix
Version: 1.2.7i1
The ntp peer check can now be configured using wato. Just use the rule "State of NTP peer" instead "State of NTP time synchronisation".
ID: 1891
Title: apc_symmetra: Now supports setting levels on remaining battery time
Component: Checks & Agents
Level: 1
Class: New Feature
Version: 1.2.7i1
The WATO rule and check have been extended to allow setting levels on remaining
battery time. Doing so is optional.
ID: 2039
Title: mk_logwatch: new per-logfile-options maxfilesize and maxlinesize
Component: Checks & Agents
Level: 1
Class: New Feature
Version: 1.2.7i1
These options allow you to truncated too long lines (in order to save space
and processing time for excessivly long lines) and to get a warning if the
size of a logfile is too large. Please refer to the online documentation
for details.