Checkmk werks level1

checkmk-werks-lvl1@lists.checkmk.com

1 participants
15886 discussions

[2.2.0] Checkmk Werk 16659 created: ldap: allow manually updating locked status of users

by Checkmk werks level 1

Title: ldap: allow manually updating locked status of users Class: fix Compatible: compat Component: wato Date: 1713947851 Edition: cre Level: 1 Version: 2.2.0p26 When using the "Authentication Expiration" sync plug-in for LDAP, users can be stuck in a locked state after too many failed login attempts. With this werk it is now allowed to edit the "Disable password" option in the UI (or "disable_login" in the REST API) for users managed by LDAP. Please note that a sync with the LDAP will restore the original value.

5 months

[2.2.0] Checkmk Werk 16805 created: mkp-tool: CLIs 'package' command

by Checkmk werks level 1

Title: mkp-tool: CLIs 'package' command Class: fix Compatible: compat Component: checks Date: 1713873479 Edition: cre Level: 1 Version: 2.2.0p26 The <code>mkp package <manifest></code> command would fail with "File conflict: /omd/sites/mydevsite/local/... (already existing)" if called in a site context. Additionally, we no longer write the mkp-tools version into the "version.min_required" field of the manifest template.

5 months

[2.4.0] Checkmk Werk 16659 created: ldap: allow manually updating locked status of users

by Checkmk werks level 1

[//]: # (werk v2) # ldap: allow manually updating locked status of users key | value ---------- | --- date | 2024-04-24T08:37:31+00:00 version | 2.4.0b1 class | fix edition | cre component | wato level | 1 compatible | yes When using the "Authentication Expiration" sync plug-in for LDAP, users can be stuck in a locked state after too many failed login attempts. With this werk it is now allowed to edit the "Disable password" option in the UI (or "disable_login" in the REST API) for users managed by LDAP. Please note that a sync with the LDAP will restore the original value.

5 months

[2.4.0] Checkmk Werk 16808 created: agent_threepar: The agent mistakenly only accepted default values as valid ones

by Checkmk werks level 1

[//]: # (werk v2) # agent_threepar: The agent mistakenly only accepted default values as valid ones key | value ---------- | --- date | 2024-04-24T14:01:07+00:00 version | 2.4.0b1 class | fix edition | cre component | checks level | 1 compatible | yes This fixes a regression in Checkmk 2.3 beta. The integration to monitor "3PAR Configuration" mistakenly only accepted any subset of the default values as valid values.

5 months

[2.4.0] Checkmk Werk 16805 created: mkp-tool: CLIs 'package' command

by Checkmk werks level 1

[//]: # (werk v2) # mkp-tool: CLIs 'package' command key | value ---------- | --- date | 2024-04-23T11:57:59+00:00 version | 2.4.0b1 class | fix edition | cre component | checks level | 1 compatible | yes The `mkp package <manifest>` command would fail with "File conflict: /omd/sites/mydevsite/local/... (already existing)" if called in a site context. Additionally, we no longer write the mkp-tools version into the "version.min_required" field of the manifest template.

5 months

[2.4.0] Checkmk Werk 16780 created: APIDocs: missing ETag response header for 2 endpoints.

by Checkmk werks level 1

[//]: # (werk v2) # APIDocs: missing ETag response header for 2 endpoints. key | value ---------- | --- date | 2024-04-24T14:41:14+00:00 version | 2.4.0b1 class | fix edition | cre component | rest-api level | 1 compatible | yes The following endpoints did not show that they returned an ETag header as part of their 200 OK response. * Show all pending changes * Show password This werk addresses this issue. Both now show the correct headers in their responses.

5 months

[2.4.0] Checkmk Werk 16803 created: Custom graphs: Fix crash in case of missing host/service/metric

by Checkmk werks level 1

[//]: # (werk v2) # Custom graphs: Fix crash in case of missing host/service/metric key | value ---------- | --- date | 2024-04-24T14:21:32+00:00 version | 2.4.0b1 class | fix edition | cee component | metrics level | 1 compatible | yes Custom graphs can contain elements whose host or service is non-existant. This happens for example when a host is removed from the monitoring after one of its metrics has been added to a custom graph. In such cases, no graph was rendered. Instead, the Checkmk UI displayed the message "Cannot calculate graph recipes" and showed a traceback. As of this werk, the UI instead renders no lines for such elements and denotes them with "n/a" in the graph legend.

5 months

[2.4.0] Checkmk Werk 16801 created: Custom graphs: Fix crash in case of unavailable scalars

by Checkmk werks level 1

[//]: # (werk v2) # Custom graphs: Fix crash in case of unavailable scalars key | value ---------- | --- date | 2024-04-23T10:22:44+00:00 version | 2.4.0b1 class | fix edition | cee component | metrics level | 1 compatible | yes When adding a scalar to a custom graph, it is possible that no value is available for this scalar. For example, this is the case when adding the CRIT threshold of a metric for which no thresholds are configured. In such cases, no graph was rendered. Instead, the Checkmk UI displayed the message "Cannot calculate graph recipes" and showed a traceback. This werk restores the correct behavior: No lines are rendered for unavailable scalars and they are denoted with "n/a" in the graph legend.

5 months

[2.4.0] Checkmk Werk 16651 created: "TSM - IBM Tivoli Storage Manager (Linux, Unix)": Agent plugin rules are merged

by Checkmk werks level 1

[//]: # (werk v2) # "TSM - IBM Tivoli Storage Manager (Linux, Unix)": Agent plugin rules are merged key | value ---------- | --- date | 2024-04-04T13:12:06+00:00 version | 2.4.0b1 class | feature edition | cee component | agents level | 1 compatible | yes Multiple matching rules of the bakery configuration ruleset "TSM - IBM Tivoli Storage Manager (Linux, Unix)" will now be merged to compute the set of effective parameters. Previously only the first matching rule was applied. During the migration to Checkmk 2.4 existing rules will be "filled", such that the outcome of the rule evaluation will not change on existing configurations.

5 months

[2.4.0] Checkmk Werk 16806 created: Handle unexpected files in 'cmk_addons/plugins'

by Checkmk werks level 1

[//]: # (werk v2) # Handle unexpected files in 'cmk_addons/plugins' key | value ---------- | --- date | 2024-04-23T12:04:08+00:00 version | 2.4.0b1 class | fix edition | cre component | checks level | 1 compatible | yes Checkmk 2.3.0 beta crashed during various operations if unexpected files where put into `local/lib/python3/cmk_addons/plugins/` or `local/lib/python3/cmk/plugins/`. They are ignored now.

5 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1