Checkmk werks level1 March 2024

checkmk-werks-lvl1@lists.checkmk.com

1 participants
258 discussions

[2.4.0] Checkmk Werk 16382 deleted: Cleanup SNMP version and bulkwalk rulesets

by Checkmk werks level 1

Werk 16382 was deleted. The following Werk is no longer relevant. [//]: # (werk v2) # Cleanup SNMP version and bulkwalk rulesets key | value ---------- | --- date | 2024-03-13T06:09:17+00:00 version | 2.4.0b1 class | fix edition | cre component | wato level | 1 compatible | no This werk is incompatible for users using the rule previously named "Disable bulk walks on SNMPv2c/v3" (see below for details). The ruleset for disabling bulkwalks has not been correctly applied to SNMPv3 hosts using the inline backend in the past. In addition it has been interfering with the ruleset to enable SNMP version 2 (over version 1). ## Change The following new ruleset _names_ are introduced: * "Disable bulkwalks" (formerly known as "Disable bulk walks on SNMPv2c/v3") * "Enable SNMPv2c for hosts" (formerly known as "Enable SNMPv2c and bulk walk for hosts") * "Enable SNMPv2c for management boards" (formerly known as "Enable SNMPv2c and bulk walk for management boards") With this change the following logic applies: * **bulkwalk**: The "bulkwalk" query is used if and only if the ruleset "Disable bulkwalks" does not match the host and it is available in the used SNMP version (v1 does not have "bulkwalk"). * **SNMP version**: Checkmk will use SNMP v3 if and only if the host configuration contains SNMP v3 style credentials. The remaining hosts will use SNMP v2c if and only if the ruleset "Enable SNMPv2c for hosts" matches, otherwise SNMPv1. This applies to both the "inline" and the "classic" backend. ## Incompatibility Previously, in order to succesfully disable SNMP bulkwalks, users had to make sure the "Disable bulk walks on SNMPv2c/v3" matched the host, and the "Enable SNMPv2c and bulk walk for hosts" did not match the host. This is no longer the case. All hosts that are neither configured for SNMPv3 (see above) nor matched by the "Enable SNMPv2c" ruleset will use SNMPv1.

6 months

[2.4.0] Checkmk Werk 16583 created: folders: Fix folders with same title were not displayed

by Checkmk werks level 1

[//]: # (werk v2) # folders: Fix folders with same title were not displayed key | value ---------- | --- date | 2024-03-14T13:43:44+00:00 version | 2.4.0b1 class | fix edition | cre component | wato level | 1 compatible | yes Before this Werk, when subfolders were listed and some of them had the same title, only the last one of the group was displayed. This Werk fixes that problem and now all folders are displayed.

6 months

[2.4.0] Checkmk Werk 16382 created: Cleanup SNMP version and bulkwalk rulesets

by Checkmk werks level 1

[//]: # (werk v2) # Cleanup SNMP version and bulkwalk rulesets key | value ---------- | --- date | 2024-03-13T06:09:17+00:00 version | 2.4.0b1 class | fix edition | cre component | wato level | 1 compatible | no This werk is incompatible for users using the rule previously named "Disable bulk walks on SNMPv2c/v3" (see below for details). The ruleset for disabling bulkwalks has not been correctly applied to SNMPv3 hosts using the inline backend in the past. In addition it has been interfering with the ruleset to enable SNMP version 2 (over version 1). ## Change The following new ruleset _names_ are introduced: * "Disable bulkwalks" (formerly known as "Disable bulk walks on SNMPv2c/v3") * "Enable SNMPv2c for hosts" (formerly known as "Enable SNMPv2c and bulk walk for hosts") * "Enable SNMPv2c for management boards" (formerly known as "Enable SNMPv2c and bulk walk for management boards") With this change the following logic applies: * **bulkwalk**: The "bulkwalk" query is used if and only if the ruleset "Disable bulkwalks" does not match the host and it is available in the used SNMP version (v1 does not have "bulkwalk"). * **SNMP version**: Checkmk will use SNMP v3 if and only if the host configuration contains SNMP v3 style credentials. The remaining hosts will use SNMP v2c if and only if the ruleset "Enable SNMPv2c for hosts" matches, otherwise SNMPv1. This applies to both the "inline" and the "classic" backend. ## Incompatibility Previously, in order to succesfully disable SNMP bulkwalks, users had to make sure the "Disable bulk walks on SNMPv2c/v3" matched the host, and the "Enable SNMPv2c and bulk walk for hosts" did not match the host. This is no longer the case. All hosts that are neither configured for SNMPv3 (see above) nor matched by the "Enable SNMPv2c" ruleset will use SNMPv1.

6 months

[2.4.0] Checkmk Werk 14226 created: Fixed stuck activate changes on bulk discovery and when using the DCD

by Checkmk werks level 1

[//]: # (werk v2) # Fixed stuck activate changes on bulk discovery and when using the DCD key | value ---------- | --- date | 2024-03-08T13:17:45+00:00 version | 2.4.0b1 class | fix edition | cme component | wato level | 1 compatible | yes Activate changes stopped working when initiating a bulk discovery or using the DCD with automatic service discovery.

6 months, 1 week

[2.4.0] Checkmk Werk 16619 adapted: Ruleset API: Ruleset validation

by Checkmk werks level 1

Werk 16619 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # Ruleset API: Ruleset validation key | value ---------- | --- date | 2024-03-11T12:46:16+00:00 version | 2.4.0b1 class | fix edition | cre component | checks level | 1 compatible | no Rulespec/ruleset names now have to be valid [python identifiers](https://docs.python.org/3/reference/lexical_analysis.html#iden… that are not [reserved keywords](https://docs.python.org/3/reference/lexical_analysis.html#keyword…. This also applies to choice identifiers in FormSpecs. The validation occurs during instantiation and will raise a `ValueError` when a violation is found. ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) # Ruleset API: Ruleset validation key | value ---------- | --- date | 2024-03-11T12:46:16+00:00 version | 2.4.0b1 class | fix edition | cre component | checks level | 1 compatible | no - Rulespec/ruleset names now have to be valid [python identifiers](https://docs.python.org/3/reference/lexical_analysis.html#iden…. + Rulespec/ruleset names now have to be valid [python identifiers](https://docs.python.org/3/reference/lexical_analysis.html#iden… that are not [reserved keywords](https://docs.python.org/3/reference/lexical_analysis.html#keyword…. This also applies to choice identifiers in FormSpecs. + The validation occurs during instantiation and will raise a `ValueError` when a violation is found.

6 months, 1 week

[2.4.0] Checkmk Werk 16619 adapted: Ruleset API: Ruleset validation

by Checkmk werks level 1

Werk 16619 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # Ruleset API: Ruleset validation key | value ---------- | --- date | 2024-03-11T12:46:16+00:00 version | 2.4.0b1 class | fix edition | cre component | checks level | 1 compatible | no Rulespec/ruleset names now have to be valid [python identifiers](https://docs.python.org/3/reference/lexical_analysis.html#iden…. The validation occurs during instantiation and will raise a `ValueError` when a violation is found. ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) # Ruleset API: Ruleset validation key | value ---------- | --- date | 2024-03-11T12:46:16+00:00 version | 2.4.0b1 class | fix edition | cre component | checks level | 1 compatible | no Rulespec/ruleset names now have to be valid [python identifiers](https://docs.python.org/3/reference/lexical_analysis.html#iden…. The validation occurs during instantiation and will raise a `ValueError` when a violation is found. -

6 months, 1 week

[2.4.0] Checkmk Werk 16619 created: Ruleset API: Ruleset validation

by Checkmk werks level 1

[//]: # (werk v2) # Ruleset API: Ruleset validation key | value ---------- | --- date | 2024-03-11T12:46:16+00:00 version | 2.4.0b1 class | fix edition | cre component | checks level | 1 compatible | no Rulespec/ruleset names now have to be valid [python identifiers](https://docs.python.org/3/reference/lexical_analysis.html#iden…. The validation occurs during instantiation and will raise a `ValueError` when a violation is found.

6 months, 1 week

[2.1.0] Checkmk Werk 16599 created: jolokia metrics: restores 'default product' behavior

by Checkmk werks level 1

Title: jolokia metrics: restores 'default product' behavior Class: fix Compatible: compat Component: checks Date: 1710165014 Edition: cre Level: 1 Version: 2.1.0p41 The check plugin no longer showed any metrics if a product was not specified in the ruleset configuration. This werk restores the original behaviour, using as a default product the one reported in the info section of the agent output.

6 months, 1 week

[2.2.0] Checkmk Werk 16494 created: netapp_ontap_temp: restore check of list of sensors

by Checkmk werks level 1

Title: netapp_ontap_temp: restore check of list of sensors Class: fix Compatible: compat Component: checks Date: 1708967815 Edition: cre Level: 1 Version: 2.2.0p24 The above-mentioned plugin now monitors the list of ambient and internal temperature sensors, sticking to the logic of the netapp_api_temp plugin (old Netapp API). A re-discovery is needed to monitor the new services.

6 months, 1 week

[2.2.0] Checkmk Werk 16460 created: Cisco Meraki: Fix getting cached organisation IDs

by Checkmk werks level 1

Title: Cisco Meraki: Fix getting cached organisation IDs Class: fix Compatible: compat Component: checks Date: 1710420761 Edition: cre Level: 1 Version: 2.2.0p24

6 months, 1 week

← Newer
1
...
12
13
14
15
16
17
18
...
26
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 March 2024