Checkmk werks level1

checkmk-werks-lvl1@lists.checkmk.com

1 participants
15874 discussions

[2.3.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.3.0p2 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.

3 months, 3 weeks

[2.3.0] Checkmk Werk 14232 created: Topology visualization: No longer crashes when trying to migrate legacy configuration to new format

by Checkmk werks level 1

[//]: # (werk v2) # Topology visualization: No longer crashes when trying to migrate legacy configuration to new format key | value ---------- | --- date | 2024-05-13T09:50:21+00:00 version | 2.3.0p2 class | fix edition | cre component | multisite level | 1 compatible | yes

3 months, 3 weeks

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

by Checkmk werks level 1

Werk 16182 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (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.3.0p2 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. ------------------------------------<diff>------------------------------------------- [//]: # (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.3.0p1 ? ^ + version | 2.3.0p2 ? ^ 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.

3 months, 3 weeks

[2.3.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.3.0p1 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.

3 months, 3 weeks

[2.3.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.3.0p2 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.`

3 months, 3 weeks

[2.3.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.3.0p2 class | fix edition | cre component | checks level | 1 compatible | yes

3 months, 3 weeks

[2.3.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.3.0p2 class | fix edition | cre component | checks level | 1 compatible | yes

3 months, 3 weeks

[2.3.0] Checkmk Werk 16427 created: cmk-update-config: Improve Handling of Implementation Errors in MKPs

by Checkmk werks level 1

[//]: # (werk v2) # cmk-update-config: Improve Handling of Implementation Errors in MKPs key | value ---------- | --- date | 2024-05-10T12:36:10+00:00 version | 2.3.0p2 class | fix edition | cre component | checks level | 1 compatible | yes This Werk affects users, which have installed an MKP with an unloadable `ValueSpec` definition. During the update process this `ValueSpec` will be loaded in order to apply an update to the corresponding rulesets. Previously, any error would cause the `RuleSet` UpdateAction to fail. With this Werk, the faulty `Ruleset` is skipped. Moreover, while `Verifying Checkmk configuration` the user is prompted with the error and can safely abort the update. This change also affects the rulesets shipped with Checkmk. However, in case a ruleset fails in this way, please report the error. This way we can address the error in the ruleset itself.

3 months, 3 weeks

[2.3.0] Checkmk Werk 16668 created: Top list dashlet: Introduce best effort querying

by Checkmk werks level 1

[//]: # (werk v2) # Top list dashlet: Introduce best effort querying key | value ---------- | --- date | 2024-05-06T08:09:18+00:00 version | 2.3.0p2 class | fix edition | cee component | multisite level | 1 compatible | yes In some rare cases, the top list dashlet does not display all available metrics due to limitations in the metric system of Checkmk. An example of this issue can be observed when using the `CPU utilization` metric. When using Windows and Linux hosts at the same time, the services of these hosts conflict with each other, potentially resulting in incomplete results. Now the top list dashlet will try to query all available metrics on a best effort basis if the results are incomplete. If some metrics are still missing, the dashlet displays an error message with the conflicting metrics. This information can be used to identify the conflicting services and exclude them by adding more filters to the dashlet.

3 months, 3 weeks

[2.3.0] Checkmk Werk 16796 created: Licensing: Start trial period when switching to CCE or CME

by Checkmk werks level 1

[//]: # (werk v2) # Licensing: Start trial period when switching to CCE or CME key | value ---------- | --- date | 2024-05-06T15:10:03+00:00 version | 2.3.0p2 class | feature edition | cme component | wato level | 1 compatible | yes When updating to an edition with mandatory licensing (CCE and CME), we want to give users enough time to apply the license when updating. A CME updated to 2.3 will now start in 30-day trial period instead of directly entering the "free" license state if it otherwise would not be licensed. However, in a distributed setup it is recommended to make use of the change in [werk #16193](https://checkmk.com/werk/16193) to apply the license before the update.

3 months, 3 weeks

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1