ID: 5476
Title: Fixed notification numbering of periodic notifications
Component: cmc
Level: 2
Class: Bug fix
Version: 1.5.0i3
Previously, non-OK state changes during periodic notifications resetted the
notification number back to 1, in effect restarting escalations. This was
inconsistent with Nagios and is not what one wants: If e.g. a service is in
WARN state for quite some time, and then goes to CRIT, one surely wants to
continue escalation, not reset it.
This problem has been fixed, so problems correctly escalate now.
ID: 5267
Title: cmk-update-agent: New binary format of Agent Updater executable on Linux
Component: agents
Level: 2
Class: New feature
Version: 1.5.0i2
The cmk-update-agent executable is now implemented as a packaged binary executable.
This werk consists of many changes that have partly already been applied to Check_MK 1.5.0i1.
The new format addresses several problems and yields some improvements:
* Better compatibility: All requirements regarding the installed Python Interpreter or other packages/programs were eliminated; the only requirements left are a x86_64 processor architecture and a glibc 2.5 or above.
* More convenient communication to Check_MK Server: All GET-Requests have been replaced with according POST-Requests. This improves security as sensitive data is no longer sent within the URL of the HTTP(S) request.
* Only one copy of cmk-update-agent: The copy of cmk-update-agent previously placed under /usr/bin/cmk-update-agent has been replaced by a shell script that executes the actual cmk-update-agent executable situated at the Check_MK Agent plugin directory. This eliminates the need to maintain two places when manually replacing cmk-update-agent for debugging reasons.
However, it is still possible to execute a copy of the cmk-update-agent executable directly.
* Notably, there will be no more problems with curl and because all communication is now done via python-requests, which is included within the cmk-update-agent executable as mentioned above.
ID: 5265
Title: cmk-update-agent: Enable Agent Updater to update itself on Windows
Component: agents
Level: 2
Class: Bug fix
Version: 1.5.0i2
When triggering an update under Windows, the agent updater could not be replaced by its new downloaded version because it was still running from the corresponding file.
This situation is now mitigated by restarting the agent updater from within ../temp when running from plugins-dir.
This is relevant only for a manual execution of cmk-update-agent.exe
ID: 5569
Title: Graph layout is now more customizable
Component: metrics
Level: 2
Class: New feature
Version: 1.5.0i2
The styling of the Check_MK graphs has now been unified for the most
places where the graphs are rendered:
<ul>
<li>Regular graph dashlets</li>
<li>Custom graph dashlets</li>
<li>Graphs in views</li>
<li>Graphs in reports</li>
</ul>
These standard render options are now available:
<ul>
<li>Font size</li>
<li>Title (Show, show inline, hide)</li>
<li>Add host/service information to title</li>
<li>Show time range of graph (top right)</li>
<li>Show margin round the graph</li>
<li>Show graph legend</li>
<li>Show vertical axis</li>
<li>Show time axis</li>
<li>Show graph controls</li>
<li>Show pin</li>
<li>Show previews</li>
<li>Colors (Background, foreground, canvas)</li>
</ul>
Some of these options are specific for the medium they are rendered
on. For example the graph controls are not available in graphs rendered
in reports. These options are hidden from the configuration.
ID: 5567
Title: Scheduled reports can now be stored in the site
Component: Reporting & Availability
Level: 2
Class: New feature
Version: 1.5.0i2
Instead of sending an email with the created report in the scheduled
interval it is now possible to store the just created reports locally
in the site.
This feature is configured in the configuration of the schedule. You
can now choose the action <i>Store locally</i> instead of
<i>Send via Email</i> and configure different action specific things
after this.
Each user allowed to use the report scheduler can open the page
"Scheduler > Stored reports" to view and open all stored reports
available to the user.
All reports are stored below <tt>~/var/check_mk/reports/archive/</tt>.
In the first directory below the base directory each user that creates
such stored reports gets a directory. All stored reports of this user
are saved below this directory. In case the user configures a schedule
to publish the resulting PDFs to other users, the reports are stored
in the <tt>public</tt> sub directory. A schedule can be configured
to store the report either directly in these directories or in a
hierarchy of subdirectories below these parent directories.
You can configure stored reports to be deleted after a given time.
ID: 5524
Title: Check API: Fix set_item_state/get_rate/get_counter logic when called from check functions
Component: Checks & agents
Level: 2
Class: Bug fix
Version: 1.5.0i2
In the 1.5.0 branch, the logic encoding the current item in the key for saved data between checks
was broken for checks with item and parse function. This did not affect the 1.4.0 branch.