Title: Notification spooler: Fix possible wrong order of notification processing
Class: fix
Compatible: compat
Component: notifications
Date: 1700481159
Edition: cee
Level: 1
Version: 2.2.0p20
The notification spooler used the mtime of the spool files to determine the
order of execution.
In rare cases, the mtime was too imprecise so we now use the mtime in
nanoseconds.
Title: Fix error on update if LDAP connection ID contains spaces
Class: fix
Compatible: compat
Component: wato
Date: 1705650557
Edition: cre
Level: 1
Version: 2.2.0p20
With werk #15815 LDAP connection IDs are validated and rewritten if they
contain spaces (possible in 2.1).
Such connection IDs resultet in sync_time files in the web dir, also containing
spaces and lead to an error on user ID validation if you update from 2.1
to 2.2.
This files are now also renamed during the update.
Title: docker_node_info: Display all errors reported by the agent plugin
Class: fix
Compatible: compat
Component: checks
Date: 1705583753
Edition: cre
Level: 1
Version: 2.2.0p20
The "Docker node info" service reports about failures of the mk_docker
agent plugin. In the past it always only reported one error per check
cycle, which now changed to displaying all reported issues.
Title: mk_docker: Prevent "Missing monitoring data for plugins" warnings
Class: fix
Compatible: compat
Component: checks
Date: 1705561042
Edition: cre
Level: 1
Version: 2.2.0p20
In case a docker node section can not be computed by the mk_docker agent plugin, the "Docker node
info" service reports about the error in detail. Until this werk, the "Check_MK" service did also
raise an issue regarding the missing agent section, like: "Missing monitoring data for plugins:
docker_node_disk_usage". This duplicate information is now suppressed, reducing the number of
notification Checkmk produces in such situations.
Title: Checkmk now redacts site secrets during support diagnostics generation
Class: feature
Compatible: compat
Component: multisite
Date: 1705564261
Edition: cee
Level: 1
Version: 2.2.0p20
Prior to this werk, generating a support diagnostic for deployments with distributed monitoring of multiple Checkmk instances would expose site secrets within the "etc/check_mk/multisite.d/sites.mk" file.
All site secrets are now replaced with "redacted" during the generation process of support diagnostics <i>(Setup > Maintenance > Support diagnostics)</i> where <i>Checkmk Configuration files</i> have been selected with at least low sensitivity or the <i>sites.mk</i> file has been selected individually.
Werk 16375 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: Rule "Check Email": Allow all makros
Class: fix
Compatible: compat
Component: checks
Date: 1705327143
Edition: cre
Level: 1
Version: 2.2.0p20
The ruleset "Check Email" recently featured stricter validation.
As a result, no makros (like <code>$HOSTNAME$</code>) could be used anymore.
This was partially compensated for in <a href="https://checkmk.com/werk/15203">#15203</a>, but this was still too restrictive.
Users can now configure validated host adresses or unvalidated strings containing macros.
------------------------------------<diff>-------------------------------------------
Title: Rule "Check Email": Allow all makros
Class: fix
Compatible: compat
Component: checks
Date: 1705327143
Edition: cre
Level: 1
- Version: 2.2.0p19
? ^^
+ Version: 2.2.0p20
? ^^
The ruleset "Check Email" recently featured stricter validation.
As a result, no makros (like <code>$HOSTNAME$</code>) could be used anymore.
This was partially compensated for in <a href="https://checkmk.com/werk/15203">#15203</a>, but this was still too restrictive.
Users can now configure validated host adresses or unvalidated strings containing macros.
Title: Rule "Check Email": Allow all makros
Class: fix
Compatible: compat
Component: checks
Date: 1705327143
Edition: cre
Level: 1
Version: 2.2.0p19
The ruleset "Check Email" recently featured stricter validation.
As a result, no makros (like <code>$HOSTNAME$</code>) could be used anymore.
This was partially compensated for in <a href="https://checkmk.com/werk/15203">#15203</a>, but this was still too restrictive.
Users can now configure validated host adresses or unvalidated strings containing macros.
Werk 16292 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: user_config: add verification for contact groups and locked attributes
Class: fix
Compatible: compat
Component: rest-api
Date: 1705416141
Edition: cre
Knowledge: doc
Level: 1
Version: 2.2.0p20
This werk introduces two changes:
LI: it now verifies for create & edit if the provided contact groups actually exist
LI: it verifies that for an edit request, locked attributes are not being modified
------------------------------------<diff>-------------------------------------------
Title: user_config: add verification for contact groups and locked attributes
Class: fix
Compatible: compat
- Component: rest-api
? -
+ Component: rest-api
Date: 1705416141
Edition: cre
Knowledge: doc
Level: 1
- Version: 2.2.0p19
? ^^
+ Version: 2.2.0p20
? ^^
This werk introduces two changes:
LI: it now verifies for create & edit if the provided contact groups actually exist
LI: it verifies that for an edit request, locked attributes are not being modified
Title: "Cisco Devices: Temperature Sensors" Revert: used wrong lower device levels
Class: fix
Compatible: compat
Component: checks
Date: 1705569737
Edition: cre
Level: 1
Version: 2.2.0p20
In Werk <a href="https://checkmk.com/werk/16276">#16276</a>, we replaced the "less than" comparison by the
"less or equal" comparison. This is not consistent with how Checkmk handles lower levels, despite
what the Werk claims. This Werk restores the old behavior before Werk
<a href="https://checkmk.com/werk/16276">#16276</a>. Note, that Werk <a href="https://checkmk.com/werk/16276">#16276</a>
also uncovered some Cisco devices, which report faulty thresholds for "less or equal". These
thresholds are now ignored again.