Werk 16680 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# Ruleset API: Changes to available rule spec topics
key | value
---------- | ---
date | 2024-04-15T06:44:00+00:00
version | 2.3.0b6
class | feature
edition | cre
component | checks
level | 1
compatible | no
This change is only relevant for plugin developers.
The available topics for rule specs have changed:
* added: `SYNTHETIC_MONITORING`
* removed: `AGENT_PLUGINS`
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
# Ruleset API: Changes to available rule spec topics
key | value
---------- | ---
date | 2024-04-15T06:44:00+00:00
version | 2.3.0b6
class | feature
edition | cre
component | checks
level | 1
compatible | no
This change is only relevant for plugin developers.
The available topics for rule specs have changed:
* added: `SYNTHETIC_MONITORING`
+ * removed: `AGENT_PLUGINS`
-
[//]: # (werk v2)
# Handle the uptime of Docker containers across time zones
key | value
---------- | ---
date | 2024-04-12T09:35:03+00:00
version | 2.3.0b6
class | fix
edition | cre
component | checks
level | 1
compatible | yes
As of version 2.3, the uptime monitoring service for Docker containers could crash if the container's start time was later than the current CheckMk site's current time. This resulted in a negative uptime calculation error (ValueError: "Cannot render negative timespan").
This could occur in situations where the host system and the container had different configured timezones.
We now correctly handle all timestamps, ensuring accurate uptime calculations regardless of timezone configurations.
[//]: # (werk v2)
# Ruleset API: Fix error during AgentConfig creation
key | value
---------- | ---
date | 2024-04-19T11:48:42+00:00
version | 2.3.0b6
class | fix
edition | cre
component | checks
level | 1
compatible | yes
When creating an `AgentConfig` rulespec using the Ruleset API an error
```
KeyError: 'cmk-match-type'
```
was raised.
Werk 16680 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# Ruleset API: Changes to available rule spec topics
key | value
---------- | ---
date | 2024-04-15T06:44:00+00:00
version | 2.3.0b6
class | feature
edition | cre
component | checks
level | 1
compatible | no
This change is only relevant for plugin developers.
The available topics for rule specs have changed:
* added: `SYNTHETIC_MONITORING`
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
# Ruleset API: Changes to available rule spec topics
key | value
---------- | ---
date | 2024-04-15T06:44:00+00:00
- version | 2.3.0b5
? ^
+ version | 2.3.0b6
? ^
class | feature
edition | cre
component | checks
level | 1
compatible | no
This change is only relevant for plugin developers.
The available topics for rule specs have changed:
* added: `SYNTHETIC_MONITORING`
[//]: # (werk v2)
# Ruleset API: Changes to available rule spec topics
key | value
---------- | ---
date | 2024-04-15T06:44:00+00:00
version | 2.3.0b5
class | feature
edition | cre
component | checks
level | 1
compatible | no
This change is only relevant for plugin developers.
The available topics for rule specs have changed:
* added: `SYNTHETIC_MONITORING`
[//]: # (werk v2)
# Custom & forecast graphs: More descriptive error messages in case of missing user input when configuring metrics
key | value
---------- | ---
date | 2024-04-19T10:57:49+00:00
version | 2.3.0b6
class | fix
edition | cee
component | metrics
level | 1
compatible | yes
When configuring the metrics rendered in custom and forecast graphs, users have to select a host,
a service and a metric. Previously, if any of these fields were missing, the Checkmk UI displayed
the message "Cannot calculate graph recipes" and an uninformative traceback. As of this werk, the UI instead displays a descriptive error message.
[//]: # (werk v2)
# Decommission legacy check API
key | value
---------- | ---
date | 2024-04-17T06:27:51+00:00
version | 2.3.0b6
class | feature
edition | cre
component | checks
level | 1
compatible | no
This werk only affects users and maintainers of custom check plugins developed against the API that was replaced in Checkmk 2.0.0.
The old API for the plugins residing in `local/share/check_mk/checks` will no longer be stable in Checkmk version 2.3.
Plugins not maintained by Checkmk will almost certainly be incompatible and therefore ignored.
Compatible plugins _will_ be considered, but the notion of what constitutes a compatible plugin may change any time.
As of Checkmk version 2.2 plugins in that folder generated a warning on the commandline and resulted in an <i>"Analyze Configuration"</i> test issueing a WARNING.
We now escalate this to CRITICAL.
Incompatible plugins are reported during `omd update`.
If you maintian such plugins, please migrate them to the new API before upgrading to Checkmk 2.3.
You can find a blog post on how to migrate these plugins
[here](https://checkmk.com/blog/migrating-check-plug-ins-to-checkmk-2-0).
A comprehensive guide on how to write plugins is found
[in our documentation](https://docs.checkmk.com/2.3.0-beta/en/devel_check_plugins.h….
Please also refer to the APIs documentation found in your site (Help -> Check plugin API reference).
Commandline call plugins for special agents and active checks in this folder will still work,
but we provide a new API for those as well now (see [Werk #16259](https://checkmk.com/werk/16259)).
They will stop working in Checkmk 2.4.
[//]: # (werk v2)
# Check certificates: Fix checking of common name of issuer
key | value
---------- | ---
date | 2024-04-18T11:02:41+00:00
version | 2.3.0b6
class | fix
edition | cre
component | checks
level | 1
compatible | yes
The active certificate check (configured via the ruleset *Check certificates*) did not check the
common name (CN) of the certificate issuer correctly:
* If only the checking of the issuer CN was activated, the CN of the subject was checked instead.
* If both the checking of the issuer and the subject CN where activated, the active check crashed with\
<code>error: the argument '--subject-cn \<SUBJECT_CN\>' cannot be used multiple times.</code>
[//]: # (werk v2)
# omd start redis: Don't Start If Process Already Running
key | value
---------- | ---
date | 2024-04-18T16:06:48+00:00
version | 2.3.0b6
class | fix
edition | cre
component | omd
level | 1
compatible | yes
With this Werk, `omd start` will no longer create a new redis process if redis is already started.
This aligns the behaviour with the other services of a site.
[//]: # (werk v2)
# Logfile pattern analyzer: Fix crash for first rule without regex pattern
key | value
---------- | ---
date | 2024-04-17T08:10:14+00:00
version | 2.3.0b6
class | fix
edition | cre
component | multisite
level | 1
compatible | yes
The "Logfile pattern analyzer" page crashed when the first "Logfile pattern" rule in place did not hold a regex pattern and a later rule did hold a regex pattern.
The rendering of the table of rules would crash with
```
Internal error: list index out of range
```
This is fixed and all rules are rendered as expected.