Title: Broken discovery result if services contained pipe symbol
Class: fix
Compatible: compat
Component: checks
Date: 1701253848
Edition: cre
Level: 1
Version: 2.2.0p16
If a services item contained the pipe symbol ("<tt>|</tt>"), the discovery check produced invalid metrics.
This resulted in a rapidly growing <tt>var/log/web.log</tt>.
Title: Automationuser login must not open full session
Class: fix
Compatible: incomp
Component: wato
Date: 1700382222
Edition: cre
Level: 1
Version: 2.2.0p16
Checkmk offers a method to authenticate single web requests with URL parameters (<tt>_username</tt> and <tt>_secret</tt>).
Due to some refactoring of the session handling with Checkmk 2.2 such automation requests initiated a full session.
The login for automation users was still blocked in the login screen but an authenticated request initiated a full session that could than be used to browse the Checkmk GUI like a regular user.
With this Werk that is no longer the case.
If you use this authentication method you should check if you rely on sessions for your automation users.
Title: KUBE: Extend `Node conditions` Rule
Class: fix
Compatible: incomp
Component: checks
Date: 1701104788
Edition: cre
Knowledge: doc
Level: 1
Version: 2.3.0b1
Previously, Checkmk identified any NodeCondition with status `True`, except for the `Ready`
condition, as a problem state. However, some Kubernetes addons report custom NodeConditions. In
some cases, the `True` status of these conditions is desired. With this Werk, this is fully
configurable.
Since there are no longer pre-defined problem states, the NodeConditions are now shown in the
summary based on their monitoring states.
The affected rule `Node conditions` has been renamed to `Kubernetes node conditions`.
The default rules ensure that the monitoring states of existing services do not change. Existing
rules are migrated. Manual intervention is only needed if there are multiple `Kubernetes node
conditions` rules, which apply the to the same service. Previously, each NodeCondition would use the
rule with a matching parameter. The new rule contains only a single parameter, thus only the first
rule applies.
Moreover, some minor tweaks have been done.
* The check falsely reported `.status.message` to be `None`. The proper message is now shown.
* NodeConditions are now shown in the order they are received from the Kubernetes API.
* The check no longer shows `NodeConditionStatus.FALSE`, instead it now shows `False`.
* The check is unaffected if one of the following conditions is missing: `Ready`, `MemoryPressure`,
`PIDPressure`, `DiskPressure`. This should not affect the monitoring since the Kubernetes API
server ensures that these conditions are always present.
Title: service_discovery: redirect response header incorrectly configured to an absolute URI
Class: fix
Compatible: compat
Component: rest-api
Date: 1700141008
Edition: cre
Level: 1
Version: 2.3.0b1
When calling the service discovery endpoint, the redirect response
header 'location' was set to an absolute URI, when it should be a
relative URI.
This werk addresses this issue by setting the URI correctly in the
redirect responses.
Title: Browsing man pages from command line
Class: fix
Compatible: compat
Component: checks
Date: 1701023104
Edition: cre
Knowledge: undoc
Level: 1
State: unknown
Version: 2.1.0p37
Viewing a check plugins man page using <tt>cmk -M my_check</tt> left the terminal in a bad state.
Browsing man pages using <tt>cmk -m</tt> did not work at all (still leaving the terminal in a bad state).
This is fixed.
After running the commands <tt>cmk -M my_check</tt> or <tt>cmk -m</tt> the tty was not properly restored.
Affected users can fix their prompt running <tt>stty sane</tt> or <tt>restore</tt>.
Title: primekey_hsm_battery_voltage: Fixed parsing of section when battery voltage is not available
Class: fix
Compatible: compat
Component: checks
Date: 1700831541
Edition: cre
Level: 1
Version: 2.2.0p16
Sometimes the battery voltage was not available or it wasn't a number. That cause the parsing of the section to fail.
This has now been fixed.
In the case of voltage being: 'External Battery: absence", the check status will be OK and the summary will provide details that the battery is absent.
If the voltage is not a number or is not absent, the voltage check will be skipped and the check result will the battery state.
Title: haproxy: Adapted HAproxy Server State and HAproxy Frontend State rules to be item specific
Class: fix
Compatible: compat
Component: wato
Date: 1700826137
Edition: cre
Level: 1
Version: 2.2.0p16
HAproxy Server State and HAproxy Frontend State were not configurable with regard to the service name.
This means that the rules were applied to all services.
This has now been adapted and the rules can be configured to apply to certain services only.
Title: Keep label filters when sorting a view
Class: fix
Compatible: compat
Component: multisite
Date: 1700564389
Edition: cre
Level: 1
Version: 2.2.0p16
When a view was filtered for host/service labels and then sorted by clicking on one of the table headers, the label filters were lost.
This is fixed to conserving the label filters when sorting a view.
Title: mk_oracle: use "${GREP}" instead of "grep"
Class: fix
Compatible: compat
Component: checks
Date: 1701070131
Edition: cre
Level: 1
Version: 2.2.0p16
When executed on solaris, <code>"grep"</code> does not know <code>-x</code> or <code>-F</code>. "${GREP}" points
to a version of grep that understands those options.
Title: Browsing man pages from command line
Class: fix
Compatible: compat
Component: checks
Date: 1701023104
Edition: cre
Knowledge: undoc
Level: 1
State: unknown
Version: 2.2.0p16
Viewing a check plugins man page using <tt>cmk -M my_check</tt> left the terminal in a bad state.
Browsing man pages using <tt>cmk -m</tt> did not work at all (still leaving the terminal in a bad state).
This is fixed.
After running the commands <tt>cmk -M my_check</tt> or <tt>cmk -m</tt> the tty was not properly restored.
Affected users can fix their prompt running <tt>stty sane</tt> or <tt>restore</tt>.