ID: 8697
Title: New report element "Multiple graphs"
Component: Reporting & Availability
Level: 2
Class: New feature
Version: 1.4.0b1
In case you want to add graphs of a dynamic collection
of services, for example all "CPU load" graphs of all hosts
that are tagged as productive hosts, you could only create
a "view" report element, specify the filters and add a single
painter showing the graphs of the service to the view. This
was working for some cases, but produced strange layout issues
in some cases. You could also not filter the single graphs of
the servvices. It was always showing all graphs of the services.
Now you can use the "Multiple graphs" report element to select
a collection of hosts/services to show the graphs. You can
configure this element to show only the N'th graphs of the
hosts/services. And you have many options to configure the
graph rendering to fit your needs now.
ID: 8677
Title: Fixed persistent recurring downtimes during cofiguration reload
Component: cmc
Level: 2
Class: Bug fix
Version: 1.4.0b1
The Check_MK Micro Core did not handle persistent recurring downtimes
correctly during configuration reloads: Already existing ones were removed
and re-added, but there was a small time window where the downtime was not
actually active (between the reload and the next time all downtimes are
handled, i.e. up to 3 seconds). This could lead to notifications during
downtimes, e.g. when a host or service was in a non-OK state during the
reload.
ID: 8678
Title: Fixed some race conditions durion CMC startup/reload
Component: cmc
Level: 2
Class: Bug fix
Version: 1.4.0b1
A few race conditions have been fixed in the Check_MK Micro Core which could
lead to e.g. spurious notifications during startup and/or configuration
reload.
ID: 8655
Title: Changing global setting for alert handler event types is now effective
Component: alerts
Level: 2
Class: Bug fix
Version: 1.4.0b2
The bug was that changing the global setting for the handled event types
would not be activated by {{Activate Changes}}. The configuration for the
core was not generated newly until some other settings was changed also.
This has been fixed.
ID: 8637
Title: Check_MK Notification Spooler is now always enabled
Component: Notifications
Level: 2
Class: New feature
Version: 1.4.0i3
The notification spooller will be enabled on all sites and can not be
disabled anymore via "omd config".
ID: 8638
Title: Fixed broken notifications when Check_MK notification spooler not enabled (regression since 1.4.0i2)
Component: Notifications
Level: 3
Class: Bug fix
Version: 1.4.0i3
When updating an existing site to 1.4.0i2 or 1.4.0i2p2 while not having the "Check_MK notification spooler"
enabled via "omd config", the notification system stopped sending notifications.
The background is that the default notification mechanism had been changed from direct delivery to
asynchronous delivery. And this was done even when the notification spooler, which is responsible for
delivering the asynchronous notification, was disabled.
The notifications are not lost, they have simply not been processed. In case you are affected,
there should exist one file for each notification that has been created but was not delivered
below <tt>var/check_mk/notify/spool/</tt>.
To fix this issue just install the new version. After the update all notification will be sent out.
In case you want to supress the stuck notifications, you can go to the directory mentioned above and
remove the <tt>.mk</tt> files in this directory before starting the site again.
To make it work for you with the existing versions, you can execute "omd config" and go to
"Distributed Monitoring > MKNOTIFYD" and enable this option. After starting the site again,
all your notifications will be processed and are sent to the users.
ID: 8634
Title: Fixed broken config when configuring "Parameters for linux_remote" ruleset
Component: alerts
Level: 2
Class: Bug fix
Version: 1.4.0i2
This fixes this error after configuring a rule for this ruleset when executing
Check_MK commands:
Cannot read in configuration file /omd/sites/heute/etc/check_mk/conf.d/wato/rules.mk: name 'alert_handler_parameters' is not defined
ID: 8622
Title: Agent Bakery: Fix broken deployment of automatic agent updater for Windows
Component: agents
Level: 2
Class: Bug fix
Version: 1.4.0i2
This bug affected builds of the 1.2.8 branch after 2016-09-14, including the
releases 1.2.8p11 and 1.2.8p12. Agents deployed with the agent bakery
of these versions do not update automatically. Redeployment to affected hosts
is required.