Checkmk werks level1

checkmk-werks-lvl1@lists.checkmk.com

1 participants
15927 discussions

[2.4.0] Checkmk Werk 16640 adapted: Ruleset API: Improve custom validation

by Checkmk werks level 1

Werk 16640 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # Ruleset API: Improve custom validation key | value ---------- | --- date | 2024-03-14T14:49:51+00:00 version | 2.4.0b1 class | fix edition | cre component | checks level | 1 compatible | no To better support the combination of different validation functions, FormSpecs now expect a sequence of validation functions instead of just one for `custom_validate`. The validation of empty inputs is now handled in the new validator `LengthInRange` instead of `DisallowEmpty`. If you used ``` custom_validate=DisallowEmpty() ``` before, use ``` custom_validate=LengthInRange(min_value=1) ``` now. For consistency, `InRange` is renamed to `NumberInRange` ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) # Ruleset API: Improve custom validation key | value ---------- | --- date | 2024-03-14T14:49:51+00:00 version | 2.4.0b1 class | fix edition | cre component | checks level | 1 compatible | no To better support the combination of different validation functions, FormSpecs now expect a sequence of validation functions instead of just one for `custom_validate`. + The validation of empty inputs is now handled in the new validator `LengthInRange` instead of `DisallowEmpty`. + If you used + ``` + custom_validate=DisallowEmpty() + ``` + before, use + ``` + custom_validate=LengthInRange(min_value=1) + ``` + now. For consistency, `InRange` is renamed to `NumberInRange`

6 months, 1 week

[2.4.0] Checkmk Werk 16640 adapted: Ruleset API: Improve custom validation

by Checkmk werks level 1

6 months, 1 week

[2.4.0] Checkmk Werk 16640 created: Ruleset API: Improve custom validation

by Checkmk werks level 1

[//]: # (werk v2) # Ruleset API: Improve custom validation key | value ---------- | --- date | 2024-03-14T14:49:51+00:00 version | 2.4.0b1 class | fix edition | cre component | checks level | 1 compatible | no To better support the combination of different validation functions, FormSpecs now expect a sequence of validation functions instead of just one for `custom_validate`.

6 months, 1 week

[2.4.0] Checkmk Werk 16629 created: Virtual host tree links work for more than three host tag groups

by Checkmk werks level 1

[//]: # (werk v2) # Virtual host tree links work for more than three host tag groups key | value ---------- | --- date | 2024-03-15T09:24:42+00:00 version | 2.4.0b1 class | fix edition | cre component | multisite level | 1 compatible | yes A virtual host tree (Setup > General > Global settings > User interface > Virtual host trees) can be configured with more than three host tag tree levels. Yet, the corresponding views that are linked to from the sidebar element "Virtual host trees" were not able to display more than three rows in the "Host tags" filter and thus only filtered for the first three. This is fixed. A virtual host tree link as described above now leads to a properly filtered view with all the given host tag filters shown in the filter popup.

6 months, 1 week

[2.4.0] Checkmk Werk 16412 created: cmk-update-config: Correct Assigning Files to Extension Package

by Checkmk werks level 1

[//]: # (werk v2) # cmk-update-config: Correct Assigning Files to Extension Package key | value ---------- | --- date | 2024-03-14T12:54:20+00:00 version | 2.4.0b1 class | fix edition | cre component | omd level | 1 compatible | yes This Werk affects those who are testing the 2.3.0 beta. It affects users, whom have enabled MKPs and then use either `omd update` or `cmk-update-config`. During the pre-update steps of Checkmk all rulesets are loaded, which are part of an MKP. Previously, if an error occurs during this step, then the user is prompted with the following error. ``` 02/05 UI extensions... Error loading rulespecs: [ValueError('cmk.plugins.redfish.rulesets.datasource: boom')] Incompatible local file 'cmk/plugins/redfish/rulesets/datasource.py'. Error: cmk.plugins.redfish.rulesets.datasource: boom You can abort the update process (A) and try to fix the incompatibilities or continue the update (c). Abort the update process? [A/c] ``` Thus, eventhough the file belongs to an MKP, if that file is part of the ruleset API v1, then Checkmk does not correctly recognize that the file belongs to an MKP during the update. Now, Checkmk offers to disable the MKP instead, i.e., ``` You can abort the update process (A) or disable the extension package (d) and continue the update process. Abort the update process? [A/d] ```

6 months, 1 week

[2.4.0] Checkmk Werk 16630 created: Prevent check_mail crash for "Move to subfolder" option

by Checkmk werks level 1

[//]: # (werk v2) # Prevent check_mail crash for "Move to subfolder" option key | value ---------- | --- date | 2024-03-18T09:19:03+00:00 version | 2.4.0b1 class | fix edition | cre component | checks level | 1 compatible | yes The active check check_mail can be configured to move mail messages from the inbox to a subfolder via the options "Forward mails as events to Event Console" > "Cleanup messages" > "Move to subfolder". For IMAP the copying of mails crashed when there were no mails available in the inbox. This is fixed to skipping the copy command in case there are no mails given.

6 months, 1 week

[2.4.0] Checkmk Werk 16645 created: Effective parameters of Check_MK Discovery

by Checkmk werks level 1

[//]: # (werk v2) # Effective parameters of Check_MK Discovery key | value ---------- | --- date | 2024-03-16T23:26:40+00:00 version | 2.4.0b1 class | feature edition | cre component | checks level | 1 compatible | yes In the page "Effective parameters of \<HOST\> / Check_MK Discovery" the parameters of the periodic service discovery where not shown. In addition some values have been shown that are not relevant to this service.

6 months, 1 week

[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, 1 week

[2.4.0] Checkmk Werk 16176 created: postfix: Fix Postfix status monitoring for agents run in Docker

by Checkmk werks level 1

[//]: # (werk v2) # postfix: Fix Postfix status monitoring for agents run in Docker key | value ---------- | --- compatible | yes version | 2.4.0b1 date | 2024-03-13T09:57:01+00:00 level | 1 class | fix component | checks edition | cre Previously, Checkmk agent used the data from /proc to determine if Postfix instance is running. Since docker containers don't have permissions to read /proc, the agent always reported the Postfix instance as 'not running'. This resulted in CRIT 'Postfix status' service even if Postfix instance was running correctly.

6 months, 1 week

[2.1.0] Checkmk Werk 16379 created: Allow disabling of bulk walks on inline SNMPv3 hosts

by Checkmk werks level 1

Title: Allow disabling of bulk walks on inline SNMPv3 hosts Class: fix Compatible: compat Component: checks Date: 1710141228 Edition: cre Level: 1 Version: 2.1.0p41 It was impossible to disable bulkwalks for SNMP version 3 hosts using the inline SNMP backend. It is fixed now in the sense that it works as in the classic backend: In order to disable bulkwalks <b>for SNMP version 3</b> hosts, you need to make sure they do <b>not</b> match the ruleset "Enable SNMPv2c and bulkwalk for host". A more thorough fix for this bug and the related phrasing in the rulesets is implemented in for Checkmk 2.3, but it was too risky to port into the stable releases. See <a href="https://checkmk.com/werk/16382">Werk #16382</a> for more on that.

6 months, 1 week

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1