Checkmk werks level1

checkmk-werks-lvl1@lists.checkmk.com

1 participants
15927 discussions

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

by Checkmk werks level 1

Title: postfix: Fix Postfix status monitoring for agents run in Docker Class: fix Compatible: compat Component: checks Date: 1710323821 Edition: cre Level: 1 Version: 2.2.0p24 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.2.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.2.0p24 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

[2.4.0] Checkmk Werk 16197 created: quantum_libsmall_*: Improve SNMP detection

by Checkmk werks level 1

[//]: # (werk v2) # quantum_libsmall_*: Improve SNMP detection key | value ---------- | --- date | 2024-02-27T12:11:36+00:00 version | 2.4.0b1 class | fix edition | cre component | checks level | 1 compatible | yes Currently the SNMP detection for `quantum_libsmall_status` and `quantum_libsmall_door` checks if "linux" and "library" are contained in the sysDescr and sysLocation OIDs. To make the detection more reliable, the sysObjectID is checked against the linux object identifier and the libraryProductName .1.3.6.1.4.1.3697.1.10.10.1.10.0 against "Quantum Small Library Product".

6 months, 1 week

[2.4.0] Checkmk Werk 16477 created: Fix crash in filesystem related Nutanix services

by Checkmk werks level 1

[//]: # (werk v2) # Fix crash in filesystem related Nutanix services key | value ---------- | --- date | 2024-03-18T09:17:45+00:00 version | 2.4.0b1 class | fix edition | cre component | checks level | 1 compatible | yes This Werk fixes a crash in the Nutanix "NTNX Storage", "Storage Pool" and "Container" services. It also adds the option to update the naming of the "Prism Alerts", "Prism Cluster", "Container" and "Storage Pool" services to be more consistent with the other Nutanix services. The new names will be automatically used in new installations.

6 months, 1 week

[2.4.0] Checkmk Werk 16476 created: add labels for Nutanix

by Checkmk werks level 1

[//]: # (werk v2) # add labels for Nutanix key | value ---------- | --- date | 2024-03-14T10:03:01+00:00 version | 2.4.0b1 class | feature edition | cre component | checks level | 1 compatible | yes This werk adds the following labels: For the host with the Nutanix special agent: * cmk/nutanix/object:control_plane For Nutanix hosts: * cmk/nutanix/object:node * cmk/os_platform:nutanix * cmk/os_name:Nutanix AHV For Nutanix VMs: * cmk/nutanix/object:vm

6 months, 1 week

[2.4.0] Checkmk Werk 16177 created: bi_aggregation: Better visualization of aggregation errors

by Checkmk werks level 1

[//]: # (werk v2) # bi_aggregation: Better visualization of aggregation errors key | value ---------- | --- date | 2024-03-15T15:27:21+00:00 version | 2.4.0b1 class | feature edition | cre component | checks level | 1 compatible | yes Aggregation errors are shown in the details of 'Aggr' services. Previously, all aggregation errors were shown in the same tree independent of whether they influence the state of the service or not, which lead to confusion. Now, two trees are shown, 'Aggregation problems affecting the state' and 'Aggregation problems not affecting the state'.

6 months, 1 week

[2.4.0] Checkmk Werk 16527 created: ldap_connection: implementation of new ldap connection endpoints

by Checkmk werks level 1

[//]: # (werk v2) # ldap_connection: implementation of new ldap connection endpoints key | value ---------- | --- date | 2024-03-07T09:59:38+00:00 version | 2.4.0b1 class | feature edition | cre component | rest-api level | 1 compatible | yes This werk implements endpoints that provide a way to manage LDAP connections via the REST-API in the same way the user interface does. This includes creating, updating, deleting and listing LDAP connections.

6 months, 1 week

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

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

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1