ID: 13124
Title: Improve usability of single systemd services discovery ruleset
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.1.0i1
The ruleset "Systemd single services discovery" allows for configuring
the discovery of single systemd services. This ruleset has been slightly
reworked to improve its usability. However, users do not need to take
any immediate action, since current configurations will continue working.
In particular, it is not possible any more to configure empty conditions
on the systemd service descriptions, unit names or states. When editing
a previously configured rule with empty conditions, users must untick
these empty conditions in order to be able to save the changes. Also,
any regular expressions are now checked for validity before saving.
Furthermore, we have added a default restriction on the unit names. This
restriction excludes the volatile systemd services check-mk-agent@.service
used by the Checkmk agent from being discovered. These services appear and
disappaer frequently, constantly resulting in vanished and undiscovered
services. Therefore, they are never discovered, indepedently of the user
configuration. See also werk #12907.
ID: 12878
Title: <tt>systemd_units</tt>: Handle "●" as marker for broken units correctly
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.1.0i1
The check plugin <tt>systemd_units</tt>, which monitors systemd units, did
not handle "●" as a marker for broken units correctly. This marker is used
when <tt>LC_ALL="C.UTF-8"</tt>, which is set by the Checkmk linux agent.
ID: 13115
Title: Fix UnicodeDecodeError on fallback notifications
Component: Notifications
Level: 1
Class: Bug fix
Version: 2.1.0i1
If locales with non UTF-8 characters were used, fallback notifications
could fail with an error like "UnicodeDecodeError: 'utf-8' codec can't decode
byte 0xe5 in position 1079: invalid continuation byte". This was seen on RHEL
based systems.
ID: 12688
Title: mssql datafiles/transactionlogs: max size reflects available filesystem size
Component: Checks & agents
Level: 1
Class: New feature
Version: 2.1.0i1
Datafiles and transactionlogs services of MSSQL databases showed "unlimited" or
the maximum configured log size as their maximum size, without taking into
account how much free space there is on the filesystem on which they are kept.
The maximum size is now capped at the available filesystem size in order to
show a true reflection of the maximum size they can take.
ID: 12521
Title: Fixed table background color and border in statistics dashlets
Component: Multisite
Level: 1
Class: Bug fix
Version: 2.1.0i1
In dashlets "Host statistics", "Service statistics" and "Event statistics" the table styling was broken. Their background color and borders are fixed again.
ID: 13237
Title: Validate input for recurring downtimes on "same day of the month"
Component: Multisite
Level: 1
Class: Bug fix
Version: 2.1.0i1
Recurring downtimes with option "same day of the month" are only handled by the
core for days 1-28 of month. The GUI will now validate the input for that
kind of downtime.
Please note that you have to revise existing recurring downtimes. Please change
the start date if it is currently 29, 30 or 31 day of month. Otherwise these downtimes
will be executed on day 28 in months without these days.
ID: 13236
Title: Fix reload of graphs if page update countdown is stopped
Component: Multisite
Level: 1
Class: Bug fix
Version: 2.1.0i1
If graphs were viewed and the page reload was paused, even if you clicked on
"stop the countdown", the page was reloaded after 60 seconds.
ID: 13233
Title: BI: Fix missing comment fields, add show more mode
Component: BI
Level: 1
Class: Bug fix
Version: 2.1.0i1
The pages for editing BI packs and aggregations had no comment field.
This was now added as "Show more" field.
The comment field for BI rules is now also only visible if show more is active.
All comment fields were also added to the REST-API.
ID: 12941
Title: REST API: convert known host attributes to well defined structure
Component: Core & setup
Level: 2
Class: Bug fix
Version: 2.1.0i1
Previously the outbound structure of host and folder attributes was not defined. The internal
structure of the values were directly passed through. This was confusing because the inbound
structure of these attributes was already defined, leading to 2 distinct structures of the same
thing.
This is no longer the case. This werk introduces documentation and validation/conversion of outbound
host and folder attributes.
Some attribute values may now be different due to this change. Please check your scripts.
ID: 12948
Title: REST API ETag handling
Component: Core & setup
Level: 1
Class: Bug fix
Version: 2.1.0i1
In 2.0.0p6, the viewing of a host through the REST API might fail
due to missing "modification time" information on the host. This led
to a HTTP 500 error. Also, the calculation of the ETag was sometimes
based on stale cached values, resulting in subsequent HTTP 412
"precondition failed" errors. This werk fixes both of these bug.