ID: 7241
Title: Fixed uploading customer logo
Component: WATO
Level: 1
Class: Bug fix
Version: 1.6.0i1
Fixed uploading customer logos for some customers. An error like this could occur: "KeyError ('globals')"
ID: 7127
Title: msexch_database: Fixed disappearance of services caused by dynamically generated IDs
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.6.0i1
After a reboot of the exchange server the databases get dynamically
generated IDs. These IDs were part of the items which led to vanished services.
This has been fixed now. You have to perform a re-discovery on the
affected hosts.
ID: 7240
Title: Fixed possible exception when filtering views using non ASCII characters
Component: Multisite
Level: 1
Class: Bug fix
Version: 1.6.0i1
A GUI timeout or UnicodeDecodeError messages could occur when trying to filter
views using non ASCII characters, like e.g. Umlauts. This could e.g. occur for
users when trying to view service detail pages of services that have such
characters in their names.
ID: 7046
Title: cisco_temperature.dom: Make power levels configurable
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.6.0i1
This werk adds support for power level configuration. Previously device configuration
specific power levels have been used only which lead to an unexpected check status in
case the devices have not been configured properly.
ID: 6658
Title: Differentiation of host & service problems notifications
Component: Notifications
Level: 1
Class: Bug fix
Version: 1.6.0i1
For REST notification plugins like Slack, PagerDuty and VictorOPS. Problems
where classified by the presence of the SERVICESTATE context variable. But
in the RAW edition this variable is completed by its macro and thus the
classification leads to host problems to be described as service problems
too. Classifying after the WHAT context variable solves the issue.
ID: 7201
Title: Servicenow: Notification plugin
Component: Notifications
Level: 2
Class: New feature
Version: 1.6.0i1
Check_MK now supports integration with Servicenow.
You can create, update and close incidents for Host an Service Problems.
Please see the inline help of the notification method rule within wato for detailed options.
CMK-1167
ID: 7217
Title: HW/SW-Inventory: Execution order of plugins
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.6.0i1
The order in which the HW/SW inventory plugins are executed is now deterministic.
Previously dependencies between inventory plugins could lead to missing data if
the plugins happend to be executed in the wrong order.
Plugins are now executed in alphabetical order by default. You can force a plugin
to be executed after another plugin by setting the <tt>depends_on</tt> key in
the inventory info variable <tt>inv_info</tt>. For instance writing
<tt>inv_info['plugin_a'] = {
...
'depends_on' = ['plugin_b'],
}</tt>
will enforce "plugin_b" to be executed before "plugin_a".
ID: 7245
Title: New builtin tag group "piggyback" allows to explictly turn piggyback data usage on/off
Component: WATO
Level: 1
Class: New feature
Version: 1.6.0i1
Piggyback data is currently only read when the host has a Check_MK service.
For some systems, the existance of the Check_MK service solely depends on the
existance of piggyback files for the given host.
During the config generation phase of the monitoring core, race conditions could apply,
where a host might receive no Check_MK service.
This werk introduces an explicit piggyback host tag, which allows you to enforce/disable the use of piggyback data.
Per default this option is currently set to <tt>Automatically detect piggyback usage</tt>, to be compatible with the previous
behaviour.
You should explictly set the <tt>Use piggyback data</tt> option if you have a ping only host,
which receives additional piggyback data from another host. This actively prevents beforementioned race conditions.