[//]: # (werk v2)
# Add support for Ubuntu 24.04 Noble Numbat
key | value
---------- | ---
date | 2024-05-13T12:42:24+00:00
version | 2.4.0b1
class | feature
edition | cre
component | deb
level | 1
compatible | yes
This werk adds support for Ubuntu 24.04, codename Noble Numbat.
[//]: # (werk v2)
# bazel_cache: Monitor Bazel Remote Cache
key | value
---------- | ---
compatible | yes
version | 2.4.0b1
date | 2023-08-03T16:51:12+00:00
level | 1
class | feature
component | checks
edition | cre
With this werk, it is possible to monitor a Bazel Remote Cache instance.
Processing data of the optional metrics and default status endpoint.
This feature consists of a special agent, agent_bazel_cache, and a new
check, bazel_cache. The special agent can be configured via the rule
Bazel Cache Metrics.
[//]: # (werk v2)
# Fix discovery state filter
key | value
---------- | ---
compatible | yes
version | 2.4.0b1
date | 2024-05-13T08:00:06+00:00
level | 1
class | fix
component | multisite
edition | cre
The filter "Discovery state" used, e.g. in the "Unmonitored services" view, was
non-functional since version 2.0. No results were shown.
[//]: # (werk v2)
# Fix host/service labels as rule conditions
key | value
---------- | ---
date | 2024-05-07T06:26:26+00:00
version | 2.4.0b1
class | fix
edition | cre
component | multisite
level | 1
compatible | yes
Due to recent changes the label conditions for rules were broken. The first label group was ignored upon form submit, and the deletion of label groups was not possible.
These two issues are fixed with this werk.
[//]: # (werk v2)
# bi: frozen node becomes CRIT and 'in service period' if the node disappeared
key | value
---------- | ---
date | 2024-04-30T13:01:42+00:00
version | 2.4.0b1
class | fix
edition | cre
component | bi
level | 1
compatible | yes
Previously, if the node of a frozen aggregation disappeared, it would
become UNKNOWN and `out of service period` instead of being removed from the tree.
Now, the node will become CRIT, but remain `in service period` in the same case.
The state was changed to alarm the user about the change in the aggregation tree better.
`out of service period` was removed because it does not apply to the entities that no longer exist.
[//]: # (werk v2)
# BI: add _clone[X] suffix to default id of cloned rule
key | value
---------- | ---
date | 2024-05-07T11:03:27+00:00
version | 2.4.0b1
class | feature
edition | cre
component | bi
level | 1
compatible | yes
To prevent saving an incorrect rule, Checkmk will now append
a `_clone[X]` suffix to the default id of the cloned rule
(`X` being an incrementing clone number).
[//]: # (werk v2)
# redefined DiscoveryParameters rulespec matching description
key | value
---------- | ---
date | 2024-05-10T06:21:23+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
This is only relevant for plugin developers.
The previously used matching description `see discovery_ruleset_type of Checkplugin` for the `DiscoveryParameters` rulespec
has been reworded as `The match type is defined by the discovery ruleset type of the check plugin.`
[//]: # (werk v2)
# BI: rule id remains editable in case of duplicate id error
key | value
---------- | ---
date | 2024-05-08T11:57:22+00:00
version | 2.4.0b1
class | feature
edition | cre
component | bi
level | 1
compatible | yes
Previously, when saving a BI rule with a duplicate id,
the action resulted in an error. But, the id field wasn't
editable anymore, forcing the user to create a new rule from
scratch.
[//]: # (werk v2)
# cisco_cpu_multiitem: Prevent exception "'item' must be a non empty string" during discovery
key | value
---------- | ---
date | 2024-05-13T06:55:38+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
[//]: # (werk v2)
# cisco_mem: Do not discover items with zero values
key | value
---------- | ---
date | 2024-05-13T06:51:14+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes