ID: 10181
Title: local: Fix "Invalid performance data" on trailing semicolons
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
When a local check reported perfdata that had one or multiple a trailing ";" signs, this could
break the local check making it show the message "Invalid performance data".
ID: 10141
Title: mk_logwatch: be more robust against unexpected file encoding
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
In version 1.6.0 the mk_logwatch plugin crashed if a processed logfile could
not be correctly encoded.
We now replace all characters that can not be encoded with the U+FFFD replacement
character. In addition, in case of an exception we now continue processing the next file.
ID: 10186
Title: Windows Agent executes 'wmi_cpuload' section separately
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.6.0p1
Previously the 'wmi_cpuload' section had been executed together with all other
sections and plugins. This could result in realistic looking, but definitely
too high numbers for the CPU load especially when the CPU is weak.
Now the Windows Agent launches the 'wmi_cpuload' section at the very beginning of
the processing cycle, both alone and synchronous, thus providing precise
results for the CPU-load.
ID: 10206
Title: check_mk_agent.solaris: Fixed missing MTIME which broke the agent data parsing
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
The MTIME for cached sections was empty such that Checkmk could not
calculate the cache age of these sections.
The fixed Solaris agent has to be deployed or installed on the
affected hosts.
ID: 10180
Title: LDAP: Fix name clashes when using multiple LDAPs with suffix and without
Component: Multisite
Level: 2
Class: Bug fix
Version: 1.7.0i1
When using the LDAP authentication with multiple LDAP servers where one of the
connections has a connection suffix configured and another does not have one
configured, it could happen that users authenticating with the suffixed
connection end up as authenticated user of the not suffixed connection.
ID: 10068
Title: graylog_messages: New check for message count of graylog indices
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.7.0i1
This check monitors the count of messages over all indices of a graylog
instance. It outputs the total number of messages and the average rate of
messages in a given timeframe.
CMK-2768
ID: 10070
Title: systemd: Fixed possible memory leak related to KillMode in unit file
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
We have seen cases in which the parameter "KillMode=process" of the unit file
"check_mk@.service" causes a memory leak. This was first seen on Debian Buster
but could occur in the future on other operating systems too.
The cached check runs that are forked in the backround seem to cause systemd
not to discard the service once it's done. If you run:
C+:
RP:systemd-cgls -au system-check_mk.slice
C-:
you can see a lot of old services and task_struct objects in slab growing
constantly. You can see those processes also on eg. Debian Stretch but there
they should have no effect on task_struct objects.
To fix this, the parameter "KillMode=process" was changed to "Type=forking".
To change the unit file:
C+:
RP:systemctl stop check_mk.socket
RP:systemctl disable check_mk.socket
C-:
Copy the new check_mk@.service unit file to /etc/systemd/system/.
You can download the file within "Monitoring Agents" - "Agent files"
or find it in site user context ~/share/check_mk/agents/cfg_examples/systemd/.
C+:
RP:systemctl daemon-reload
RP:systemctl enable check_mk.socket
RP:systemctl start check_mk.socket
C-:
ID: 10174
Title: Add Web-API calls for Checkmk Grafana datasource 1.1.0
Component: metrics
Level: 2
Class: New feature
Version: 1.7.0i1
The upcoming version 1.1.0 of the Checkmk Grafana datasource
(https://github.com/tribe29/grafana-checkmk-datasource/)
will introduce some new features that need these new API calls:
<ul>
<li>get_combined_graph_identifications: Used to aggregate similar graphs
of the same type together to a single value</li>
<li>get_graph_annotations: Used to add some monitoring events as Grafana
annotations to dashboards.</li>
</ul>
ID: 10179
Title: Discovery page: Missing "full scan" button in some cases
Component: WATO
Level: 1
Class: Bug fix
Version: 1.7.0i1
In previous 1.6 releases the message "No discovery information available.
Please perform a full scan." could appear without a visible "Full scan"
button could appear making it hard to proceed with a service discovery.
As a workaround with previou versions, you could execute a bulk discovery for
this host or go on the diagnostic page and click on the "Test" button once.
Afterwards you should be able to proceed on the discovery page.