ID: 5599
Title: check_dns: Return to the behaviour prior to Werk #5526
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.4.0p23
Although Werk #5526 brought the behaviour in line with what's described in the GUI,
this kind of change requires further discussion as to what the desired behaviour is.
We return to the old behaviour and adjust the GUIs description
ID: 5598
Title: postfix_mailq_status: Fix Linux agent to handle newer SuSE systems
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.5.0i3
Postfixes master executable can be found under postfix/sbin or postfix/bin
depending on the system. The latter case had not been handled by the agent.
This has been fixed.
Thanks to Robert Sander for the patch!
ID: 5550
Title: mk_oracle.ps1: Fixed exceptions because of useless backslashes
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.5.0i2
There has been a bug introduced as part of a feature enhancement which
caused an exception of the plugin and prevented the execution. This bug has
been introduced in June 16th and is solved now.
ID: 5485
Title: alcatel_power: improved detection of power supplies on newer devices
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.5.0i3
Previously, the power supplies were detected based on the module type id.
Now the power supplies are detected through the more specifig power supply
type. The module type is only used as a fallback when the power supply
type is not available.
ID: 5294
Title: mk_sap_hana: New plugin which monitors SAP HANA instances
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.5.0i1
#TODO
ID: 5476
Title: Fixed notification numbering of periodic notifications
Component: cmc
Level: 2
Class: Bug fix
Version: 1.5.0i3
Previously, non-OK state changes during periodic notifications resetted the
notification number back to 1, in effect restarting escalations. This was
inconsistent with Nagios and is not what one wants: If e.g. a service is in
WARN state for quite some time, and then goes to CRIT, one surely wants to
continue escalation, not reset it.
This problem has been fixed, so problems correctly escalate now.
ID: 5475
Title: Do not suppress recovery notifications via throttling.
Component: cmc
Level: 1
Class: Bug fix
Version: 1.5.0i3
When notification throttling was enabled, recovery notifications were not
handled specially, so they could be suppressed just like problem
notifications. This has been fixed, revovery notifications always pass
through throttling now.
ID: 5474
Title: Revocery notifications have at least notification number 1
Component: cmc
Level: 1
Class: Bug fix
Version: 1.5.0i3
When periodic notifications were off, recovery notifications were sent out
with notification number 0. This is different from what nagios does and it
is inconsistent: Recovery notifications should have the same notification
number as their corresponding problem notification. This has been fixed,
the recovery notification numbers are now always at least 1, perhaps greater
in case of periodic notifications.