ID: 8389
Title: Zooming/panning graphs pauses page updates now
Component: metrics
Level: 2
Class: Bug fix
Version: 1.4.0i1
To prevent issues with the graphs during view / dashlet data updates the updates
are paused for 60 seconds. If you don't modify the graph in this time, the whole
page will be reloaded and the graph is reset to it's original time and vertical
scaling.
The paused update is visualized with a large pause overlay on the top/right of
the screen. This overlay shows a countdown of seconds left until the page update
is continued by reloading the whole page.
ID: 8378
Title: Added graph overview page with time range selection for graphs of hosts/services
Component: metrics
Level: 2
Class: New feature
Version: 1.2.7i4
A new view has been added for getting an overview on all graphs of a service. This
replaces the graph page of PNP4Nagios and completes integration of the new graphing
system.
ID: 8362
Title: Improved error handling in case of upgrades/downgrades
Component: Core & setup
Level: 2
Class: Bug fix
Version: 1.2.7i4
CMC stores its current state in versioned state files, which are only
downwards-compatible. When an incompatible state file is found, we
immediately terminate the monitoring core during startup.
<ul>
<li>When the state file version is older than the current one (e.g. after
an upgrade), convert it on the fly (as previously), but keep a backup of the
previous version in "state-version-XY".</li>
<li>When the state file version is newer than the current one (e.g. after a
downgrade), emit an error message, hinting at the backup version if there is
one.</li>
</ul>
ID: 8359
Title: Manage Extension Packages (MKPs) via WATO
Component: WATO
Level: 3
Class: New feature
Version: 1.2.7i4
WATO now has a new module for managing Check_MK Extension Packages (MKPs) via WATO.
The new module helps you to create MKPs and also allows you to install MKPs (e.g.
from <a href="http://exchange.check-mk.org">The Check_MK Exchange</a>. MKPs can also
be distributed to your slave sites.
ID: 8360
Title: Recurring downtimes now for nth day of month and xth weekday from beginning and end
Component: Multisite
Level: 2
Class: New feature
Version: 1.2.7i4
The recurring scheduled downtimes can now be set to appear always on the
same day of the month, e.g. always on the first of the month. Also you
can choose them to happen on each first, second, third or fourth Monday,
Tuesday, etc. Also couting from the end of the month is possible, e.g. each
last friday in the month.
ID: 8358
Title: Automatic Check_MK Agent updates for Linux
Component: agents
Level: 3
Class: New feature
Version: 1.2.7i4
The Check_MK Agent Bakery now allows for automatically updating Check_MK
Agents via HTTP/HTTPS. This is realized by a new agent plugin called
<tt>cmk-update-agent</tt>, that is currently only available for Linux,
but a Windows version will follow soon. The steps for setting up the
automatic updates is:
1. Go to the new page for the Agent Deployment. You find a new button
for this in the Agent Bakery page.
2. Fullfil all of the prerequisites that are shown on that new pages.
This involves creating agents that contain the new plugin with a
valid configuration and enabling the deployment.
3. Install the new prepared agents on the target hosts of your choice.
4. Call <tt>cmk-update-agent register</tt> on these systems in order
to register the agents for updates.
5. Don't forget to enable the agent deployment's master switch!
ID: 8355
Title: Fixed exception about "TypeError: a float is required" in reporting
Component: Reporting & Availability
Level: 2
Class: Bug fix
Version: 1.2.7i4
This occurred when selecting time ranges of the form <i>The last ...</i>.
ID: 8354
Title: Notification spooler: handle incoming connections even in situation with large spool directories
Component: Notifications
Level: 2
Class: Bug fix
Version: 1.2.7i4
In situations where a large bulk of notification came in from a slave the mknotify
would happily handle all those notifications while at the same time forgetting
to handle all the connections. They would run into timeouts that way. No the
processing of notifications is limited to 3 seconds for each turn.