ID: 11341
Title: Make omd restore work with hardlinks in local dir
Component: Site Management
Level: 1
Class: Bug fix
Version: 1.7.0i1
In case a backup file was created from a site which contained hardlinks in the local directory, the restore mechnism will crash with the following message:
<code>KeyError: "linkname 'SITE-NAME/local/LINK-NAME' not found"</code>
This werk will enable resolving hard links which reside under the local directory.
ID: 11303
Title: mem.linux: false CRIT status when VmallocChunk is set to 0 kB
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
On Linux kernel 5.3 and newer versions, VmallocChunk is not set (i.e. set to
0 kB). This causes the plugin to report a false CRIT status when evaluating the
status of 'Largest Free VMalloc Chunk'. We have amended the plugin to ignore
Vmalloc Chunk if it is set to 0 kB.
ID: 11262
Title: Activate changes: Asking for activation comment can now be configured
Component: Multisite
Level: 1
Class: New feature
Version: 1.7.0i1
The comment that can be added before activating the pending changes is now
configurable using the global setting "Ask for a comment for activation of changes".
You can either choose to enforce your users to provide a comment, ask for an
optional comment or completely skip the question for a comment.
The default has been set to: "Do not ask for a comment".
ID: 11302
Title: Azure Storage: egress data levels wrongly labelled on user interface
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
The egress data levels parameters of the Azure Storage plugin were labelled
'ingress data'. This has been fixed.
ID: 11261
Title: Fix performance regression caused by too many live status queries between EC and core
Component: Event Console
Level: 2
Class: Bug fix
Version: 1.7.0i1
The version 1.6.0p14 introduced an issue affecting the Event Console and it's
Livestatus communication with the local monitoring core.
Instead of querying static configuration related information, which is needed
by the Event Console only once per core restart, these information were not
cached as intended. This resulted in these queries being made over and over
again.
The query was executed in the following situations:
<ul>
<li>Multiple times when querying the "eventconsolestatus" table (Once for each host known by the Event Console)</li>
<li>Once for each created event</li>
</ul>
ID: 10544
Title: Quicksearch: Fixed incorrect result page when querying host tags
Component: Multisite
Level: 1
Class: Bug fix
Version: 1.7.0i1
The filter <tg:> was incorrectly evaluated when the result set included mulitple hosts.
ID: 11360
Title: juniper_temp: Discover on additional devices
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.7.0i1
The check <tt>juniper_temp<\tt>, which monitors the temperatures
of modules of Juniper devices, is now discovered on additional
devices such as EX3400-48t switches.
ID: 11144
Title: Display graph for SAP HANA License
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
The checkplugin "sap_hana_license" was not generating the graphs for "Used licenses" and "Size of license". This was fixed with this werk.
ID: 11051
Title: crash in notifications if "Exclude Service Groups (regex)" is used
Component: Notifications
Level: 1
Class: Bug fix
Version: 1.7.0i1
If a notification rule used the option "Exclude Service Groups (regex)" and
no service group was defined for a service the notification rule processing
crashed. In the var/log/notify.log a traceback that contains the line
"TypeError: 'NoneType' object has no attribute '__getitem__'" was shown.
This is fixed.
ID: 11234
Title: Check_MK service: State if "Unexpected allowed IP ranges" is configurable
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.7.0i1
If a Checkmk site is updated to a newer version but the agents of Windows hosts
are not, then the warning {{Unexpected allowed IP ranges}} may be displayed in
the details of the {{Check_MK}} service and the service state changes to
{{WARN}} (by default).
With this setting you can overwrite the default service state. This will help
you to reduce above warnings during the update process of your Checkmk sites
and agents.
We recommend to set this option only for the affected hosts as long as you
monitor agents older than Checkmk 1.7. After updating them, you should change
this setting back to it's original value.