Checkmk werks level1 May 2024

checkmk-werks-lvl1@lists.checkmk.com

1 participants
549 discussions

[2.4.0] Checkmk Werk 16022 created: bazel_cache: Monitor Bazel Remote Cache

by Checkmk werks level 1

[//]: # (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.

4 months, 1 week

[2.4.0] Checkmk Werk 16704 created: Fix discovery state filter

by Checkmk werks level 1

[//]: # (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.

4 months, 1 week

[2.4.0] Checkmk Werk 16635 created: Fix host/service labels as rule conditions

by Checkmk werks level 1

[//]: # (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.

4 months, 1 week

[2.4.0] Checkmk Werk 16182 created: bi: frozen node becomes CRIT and 'in service period' if the node disappeared

by Checkmk werks level 1

[//]: # (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.

4 months, 1 week

[2.4.0] Checkmk Werk 16184 created: BI: add _clone[X] suffix to default id of cloned rule

by Checkmk werks level 1

[//]: # (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).

4 months, 1 week

[2.4.0] Checkmk Werk 16764 created: redefined DiscoveryParameters rulespec matching description

by Checkmk werks level 1

[//]: # (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.`

4 months, 1 week

[2.4.0] Checkmk Werk 16185 created: BI: rule id remains editable in case of duplicate id error

by Checkmk werks level 1

[//]: # (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.

4 months, 1 week

[2.4.0] Checkmk Werk 16740 created: cisco_cpu_multiitem: Prevent exception "'item' must be a non empty string" during discovery

by Checkmk werks level 1

[//]: # (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

4 months, 1 week

[2.4.0] Checkmk Werk 16739 created: cisco_mem: Do not discover items with zero values

by Checkmk werks level 1

[//]: # (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

4 months, 1 week

[2.2.0] Checkmk Werk 16757 created: agent_kube: resolve case when referenced PVC is no longer present

by Checkmk werks level 1

Title: agent_kube: resolve case when referenced PVC is no longer present Class: fix Compatible: compat Component: checks Date: 1714992435 Edition: cre Level: 1 Version: 2.2.0p27 Prior to this werk, the Kubernetes special agent failed whenever the API returned Kubernetes objects with at least one reference to a no longer existing PVC. This werk fixes this issue by ignoring such references.

4 months, 1 week

← Newer
1
...
47
48
49
50
51
52
53
54
55
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 May 2024