ID: 13946
Title: Add Kubernetes icon to menu entries
Component: Multisite
Level: 1
Class: Bug fix
Version: 2.2.0i1
With this werk, an icon is shown next to the menu item Kubernetes in the Dashboards menu.
ID: 14118
Title: Notification spooler: Fix execution of notifications on sites only forwarding
Component: Notifications
Level: 1
Class: Bug fix
Version: 2.2.0i1
On sites which had the option "Forward to remote site by notification spooler"
configured, the answer of the target site also lead to execution of of the
notification at this site, leading to duplicated notifications.
Furthermore, the result of the execution was not logged to history.
ID: 13014
Title: Fix agent proxmox bug if duration is more than 24 hours
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
Fix a bug if duration string is more than 24 hours
CMK-9146
In a rare occasion if the backup takes more than 24
hours the standard datetime string parsing fails.
So the manual parsing and feeding bits to timedelta object
solves the problem
ID: 13987
Title: job: replace useless start time metric with job age
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
The check plugin job, which monitors cronjobs running with mk-job, produced
a useless metric measuring the unix time stamp at which the job had been started.
This metric has now been replaced with a new metric job age, which measures the
actual age of the job.
ID: 14090
Title: Unknown enforced services on clusters
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
This fixes a regression in Checkmk versions 2.0.0 - 2.0.0p25.
Enforced services on a cluster would go to UNKNOWN if the corresponding services were not additionally configured to be clustered on at least one node.
This werk restores the original behaviour, where in such cases the data of <b>all</b> nodes is passed to the clustered service.
ID: 14075
Title: Prometheus special agent: Handle credentials from password store correctly
Component: agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
The Prometheus special agent did not handle credentials from the password
store correctly, leading to connection failures.
ID: 14076
Title: Alertmanager special agent: Handle credentials from password store correctly
Component: agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
The Alertmanager special agent did not handle credentials from the password
store correctly, leading to connection failures.
ID: 14078
Title: Fix deletion of users with none-ASCII characters in distributed setups with configuration replication
Component: Multisite
Level: 1
Class: Bug fix
Version: 2.2.0i1
In distributed setups with configuration replication, deleting a user with none-ASCII
characters in its username led to a crash upon attempting to activate the change:
<tt>cmk.gui.exceptions.MKUserError: The given text must only contain ASCII characters.</tt>
ID: 14077
Title: NagVis Geomaps: Deprecate <tt>wato_geo_fields.py</tt> in favor of regular custom host attributes
Component: Setup
Level: 1
Class: Bug fix
Version: 2.2.0i1
This werk only affects users of NagVis Geomaps.
One of the available map types in NagVis are Geomaps, which show geographical locations.
For this map type, NagVis offers the option to use geographical coordinates stored in
Checkmk host attributes, see http://docs.nagvis.org/1.9/en_US/geomap.html.
The necessary host attributes (latitude and longitude) are by default not available in
Checkmk. Therefore, up to now, Checkmk came with the script
<tt>share/doc/check_mk/treasures/wato_geo_fields.py</tt>,
which added these host attributes.
As of this werk, <tt>wato_geo_fields.py</tt> is deprecated, since it is incompatible
with Checkmk 2.1. Attempting to use this script in version 2.1 will fail, meaning that
latitude and longitude will no longer available in the user interface. Furthermore, the
REST API will respond with HTTP 500 when attempting to query the status of affected
hosts.
To retain the functionality previously offered by this script, users can instead create
two regular custom host attributes. This is fully compatible and will not result in any
loss of data. The exact procedure is described here:
https://kb.checkmk.com/display/KB/Geo+coordinates+from+Checkmk+in+NagVis+ma….
After creating the custom attributes, users must remove their local copy of
<tt>wato_geo_fields.py</tt> from <tt>local/share/check_mk/web/plugins/wato/<tt>.