ID: 2365
Title: Removed old deprecated notification global options for plain emails
Component: WATO
Level: 2
Class: New Feature
Version: 1.2.7i3
The global settings for old plain email notifications (like configuring the
subject) have been removed. The will not work for the current rule based
notifications anyway. If you really still use plain emails then your old
settings will continue to work for the while, though. We encourage you to
switch over to rule based notifiations.
ID: 2352
Title: FreeBSD Agent: Removed statgrab cpu section because there is a dedicated cpu section
Component: Checks & Agents
Level: 2
Class: Bug Fix
Version: 1.2.7i3
Removed the <tt>statgrab_cpu</tt> section from the agent because there is a standard
conform <tt>cpu</tt> section in the agent.
If yoy used the <tt>statgrab_cpu</tt> check before and have disabled the <tt>cpu</tt>
check on your devices by configuration, you will need to remove the "disabled services"
or "disabled checks" rules from your hosts.
ID: 2350
Title: FreeBSD Agent: Changed bash path to /usr/local/bin/bash
Component: Checks & Agents
Level: 2
Class: Bug Fix
Version: 1.2.7i3
Older versions of the FreeBSD Agent used the /bin/bash path as interpreter
which seem not to be standard conform. It has now been changed to
<tt>/usr/local/bin/bash</tt> in the hope that this is now correct and not
breaking existing setups.
ID: 2351
Title: FreeBSD Agent: Made plugin/local paths standard conform
Component: Checks & Agents
Level: 2
Class: Bug Fix
Version: 1.2.7i3
The former paths <tt>/usr/lib/check_mk_agent</tt> were not correct according
to FreeBSD standards. We have now switched the path to <tt>/usr/local/lib/check_mk_agent</tt>.
If you currently use the old paths, you will need to move this directory to
the new location when using the new agent.
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.