ID: 14684
Title: Fixed handling of Livestatus socket specification in livedump/cmc
Component: Livestatus
Level: 1
Class: Bug fix
Version: 2.2.0i1
There were a few tiny bugs plus some surprising behavior when specifying the
Livestatus socket for livedump/cmcdump. With this change, the rules are
simple and consistent now: If there is a -s/--socket commandline option, use
that. Otherwise derive the UNIX socket from the OMD_ROOT environment
variable if that is set (probably the common case). And finally: If there
is no -s/--socket option and no OMD_ROOT, complain and exit.
ID: 13433
Title: Enable bakery to configure redis to use socket connection instead of tcp
Component: Checks & agents
Level: 1
Class: New feature
Version: 2.2.0i1
The configuration file of mk_redis.py already had a way to specify a socket
connection, but it was not possible to configure this via the bakery.
ID: 14864
Title: Docker monitoring: Prevent intermittent alerts due to race conditions
Component: agents
Level: 1
Class: New feature
Version: 2.2.0i1
If a docker container or image is removed while the docker agent plugin is collecting data, it could lead to temporary alerts such as "no such image"/"no such container" in the node info service and "count not present in agent output" in the containers service.
The agent plugin now handles such cases without producing any alerts.
ID: 14936
Title: logwatch: fix validation for REWRITE state
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
The validation fot the REWRITE state in the Text logfiles rule
(logwatch plugin) was erroring out when the patterns contained a
reference to the previously matched groups.
This werk fixes the issue.
ID: 14625
Title: fortigate_sync_status: No longer crashes if the status is not available or is not known
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
The check used to crash if the status of a cluster was not available (i.e. empty string) or
if the status was not known (wasn't either 'synchronized' or 'unsynchronized').
Now, if any of the above cases occur, the check turns to an UNKNOWN state and provides the appropriate description.
ID: 14298
Title: Remove Web API
Component: Setup
Level: 2
Class: New feature
Version: 2.2.0i1
With Checkmk 2.1, announced by Werk #13640, the Web API was deprecated. This
release now removes the Web API.
We recommend migrating all existing scripts that use the Web API to the REST
API.
ID: 14627
Title: storcli_vrdives: KeyError(<ITEM>) raised in the check function if the item vanished
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
storcli_vrdives check function did not check for the existence of an item in the preprocessed
data and raised KeyError() in case it didn't exists. This change aborts the check resulting
in UNKN state in that case.
ID: 14648
Title: Pre 2.0 bakery plugins are no longer supported
Component: agents
Level: 1
Class: New feature
Version: 2.2.0i1
This werk only affects users with custom bakery plugins that have not been migrated to the new plugin API (introduced in Checkmk version 2.0).
As announced in Werk #11401 the support for legacy bakery plugins (used in Checkmk version 1.6 and earlier) is now dropped.
To see if this affects you, you can grep for the string "<tt>bakery_info[</tt>" in your <i>local/share/checkmk</i> folder.
Help on how to migrate these plugins can be found in the "<i>Plugin API reference</i>" section of the sites help menu.
ID: 14872
Title: mk_logwatch plugins correctly reports changes on Windows
Component: Checks & agents
Level: 2
Class: Bug fix
Version: 2.2.0i1
Previously, mk_logwatch plugin may wrongly report as changed
the whole content of a log file. The source of the problem was
an unstable file identification algorithm on Windows.
With this release logwatch plugin on Windows always correctly
deteremines changed part of monitored file.
ID: 13959
Title: REST API: Create users with custom attributes
Component: REST API
Level: 1
Class: Bug fix
Version: 2.2.0i1
The POST method of the "/domain-types/user_config/collections/all" endpoint
has been extended to allow you to create users with custom attributes.
Please note that the attributes must have been already defined by other means
such as the GUI.
Due to technical limitations, the ReDoc/Swagger documentation won't show custom
attributes in neither the schema nor the examples.