ID: 12699
Title: Activate Livestatus TCP socket with systemd on recent enough systems
Component: Core & setup
Level: 1
Class: New feature
Version: 2.1.0i1
The Livestatus socket can be configured to be reachable over the
network (details can be found under
https://docs.checkmk.com/latest/en/livestatus.html#network).
This is needed for, e.g., building distributed environments with Checkmk.
In previous releases this network connection was managed by a
site-specific xinetd instance. Since xinetd is not available on newer
Linux distributions, we have added an alternative mode of managing
the socket using systemd.
All Checkmk sites on Linux distributions with a systemd version newer or
equal to version 235 that have the LIVESTATUS_TCP option enabled (see
abover for a link to the manual) automatically and seamlessly switch to
the new systemd-managed socket after upgrading to Checkmk 2.1. Older
Linux distributions keep using xinetd.
Users are advised to double-check the systemd configuration under
<tt>$OMD_ROOT/etc/mk-livestatus/livestatus.socket</tt> and
<tt>$OMD_ROOT/etc/mk-livestatus/livestatus@.service</tt>.
ID: 13360
Title: No longer allow semicolon in service descriptions
Component: Core & setup
Level: 1
Class: Bug fix
Version: 2.1.0i1
When having a semicolon in service description the metric
system would break i.e. metrics for this service would not be displayed.
Having a semicolon in service description was not allowed before 2.0 but
this restriction has been removed with Werk #12799.
>From now on the semicolon will again be removed from service descriptions.
With this change all services containing a semicolon will be renamed after
the next "Activate changes"
Notice: You are only affected by this issue if you are using the Checkmk Microcore
ID: 13313
Title: Distributed monitoring: Improve version compatibility validation
Component: Setup
Level: 1
Class: New feature
Version: 2.1.0i1
In distributed setups with sites using different Checkmk versions we can
not ensure that all versions are compatible with each other. To clarify
the compatibility between version we've now added more version checks that
ensure the central and remote sites are using compatible versions.
Allowed are connections:
<ul>
<li>Between same major versions (e.g. 2.0.0p1 to 2.0.0p3)</li>
<li>From previous to newer major version (e.g. 1.6.0 central to 2.0.0 remote site)</li>
</ul>
Disallowed are connections:
<ul>
<li>From pre-pre to new major version (e.g. 1.6.0 central to 2.1.0 remote site)</li>
<li>From new to old (e.g. 2.0.0p1 to 1.6.0p21)</li>
<li>Between CME and other editions</li>
</ul>
ID: 12700
Title: Fix false positives and high CPU for smart ping
Component: Core & setup
Level: 1
Class: Bug fix
Version: 2.1.0i1
A timeout from a host being checked by smart ping could result in
100% CPU usage for the process and the program would stop working
properly. This may in turn result in false positives for some hosts.
ID: 12334
Title: Windows agent displays help text correctly
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.1.0i1
Previously, Windows agent being started from command line without an argument
printed the help text incorrectly: the agent called asynchronously the internal
protection script.
With this release the problem has been solved. Windows agent calls protection
script only being started as a service.
ID: 12959
Title: contact group host attribute in REST API
Component: Core & setup
Level: 1
Class: Bug fix
Version: 2.1.0i1
Previously, the contact_group attribute could not be set, because it
lead to an error. This has been fixed and it can now be set. The REST
API documentation has been updated as well.
Please note that, if you're using a statically typed language and a
generated API client, you may have to regenerate your API client library.
ID: 12958
Title: add validation for custom tags to REST API
Component: Core & setup
Level: 1
Class: Bug fix
Version: 2.1.0i1
Previously, host attributes which were custom defined could not be used
in the REST API due to a missing validation step. This Werk fixes this.
Custom attributes can now be used in the REST API as soon as they are
created (e.g. using the Setup GUI).
ID: 13377
Title: Fix missing date header in for ASCII and HTML Email
Component: Notifications
Level: 1
Class: Bug fix
Version: 2.1.0i1
The Date header is usually added by the local MTA and does not cause any problems.
However, if direct delivery via SMTP smart host is set, the date header is no
longer added and is then missing in the mail client, which shows the date of
receipt.
ID: 13037
Title: Add dashlet to display inventory attribute
Component: Setup
Level: 1
Class: New feature
Version: 2.1.0i1
Add a dashlet to display a single inventory element.