ID: 2357
Title: livestatus_status: no not alarm switched off host freshness nor event handlers on CMC <= 1.2.6
Component: Checks & Agents
Level: 2
Class: Bug Fix
Version: 1.2.7i2
CMC version 1.2.6 did not have event handlers. So they are always switched
off. The check will no longer warn about this. Host freshness checking is
turned off per default in OMD based installations for the Nagios core. Per
default alerting this also has been disabled.
ID: 2354
Title: BI aggregations now also consider the service period
Component: BI
Level: 2
Class: New Feature
Version: 1.2.7i2
BI aggregations now also consider the service period of their contained
services and hosts - just like for downtimes and acknowledgements. A BI
aggregate is thus considered to be within its service period if its state
would be OK under the assumption that all objects that are currently out
of their service period are CRIT and the rest is OK. Or otherwise stated:
If all things that are not in their service period are switched off: if the
BI aggregate would get CRIT - well then it is not in its service period.
Yet in other words that means that the service period of something can only
cover times where all of its vital parts also are in service period.
The information "within/out of service period" is now also available for
the availability computations. That allows you now to base availability
reporting for BI aggregates to be based on certain time periods.
ID: 2332
Title: New icon for hosts/services that are out of their service period
Component: Multisite
Level: 2
Class: New Feature
Version: 1.2.7i2
The service period defines the times of the day that a service is expected
to by up. This is mainly being used for availability computations but can
also be used for filtering out unimportant things during non-work-hours.
ID: 2328
Title: Fix sporadic error "Connection reset by peer" when reloading Event Console
Component: Event Console
Level: 2
Class: Bug Fix
Version: 1.2.7i2
The problem appeared especially when distributing changes with WATO in a
distributed setup. The reason was: the reload of the configuration closed
and reopened the UNIX socket that is used for sending commands. That way
parallel connections would be closed. Now the UNIX socket is only reopened
when the configuration parameter <i>Max. number of pending connections to
the status socket</i> has changed and a reload is thus neccessary in order
to make that change active.
ID: 2323
Title: df: Fix new graphs for all filesystem checks in case of existing inode information
Component: Checks & Agents
Level: 2
Class: Bug Fix
Version: 1.2.7i2