ID: 8304
Title: New graphical frontend for metrics time graphs
Component: Metrics System
Level: 3
Class: New Feature
Version: 1.2.7i3
The Check_MK Enterprise Edition has now a new graphical user frontend for
displaying metrics time graphs. Instead of using pixeled PNG images it makes
use of interactive vector graphics using HTML 5. These graphs do not only
look better. They allow you to:
LI:Zoom horitontally using your mouse wheel
LI:Zoom vertically by dragging points up and down
LI:Scroll horizontally (into past and future) by dragging points left and right
LI:Resize a graph using the right bottom corner
If more than one graph is being displayed on the same HTML page then any zoom
or shift in time will be synchronzed to <b>all</b> graphs on the same page.
Also the reporting uses the new graphing engine and replaces the embedded
pixel images by real vector graphics.
ID: 8358
Title: Automatic Check_MK Agent updates for Linux
Component: Agent Bakery
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: 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: 8394
Title: New graph designer for creating custom graphs
Component: Metrics System
Level: 3
Class: New Feature
Version: 1.2.7i4
With the new custom graphs you can now create performance graphs with arbitrary
metrics from arbitrary hosts and services. That way you can e.g. create a graph
for showing HTTP response times from three different servers in one graph.
The new custom graphs can be added to reports, graph collections and dashboards.
There are several paths to the graph designer:
LI:Click on the context menu of an existing graph and select <i>Add all metrics of this graph to: new custom graph</i>
LI:Go to a host or service detail, there to <i>Service Metrics</i>, use the small icon of one metric and select <i>Add this metric to custom graph...</i>
LI:Press <i>EDIT</i> in the Views, Bookmarks or Reports-Snapin and click the new button <i>Custom Graphs</i> at the top
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.