Checkmk werks level1 February 2024

checkmk-werks-lvl1@lists.checkmk.com

1 participants
287 discussions

[2.2.0] Checkmk Werk 16327 created: netapp_ontap_environment: show unit of measurement in summary

by Checkmk werks level 1

Title: netapp_ontap_environment: show unit of measurement in summary Class: fix Compatible: compat Component: checks Date: 1706794456 Edition: cre Level: 1 Version: 2.2.0p22 The service summary now displays the units of measurement of the monitored value.

7 months, 1 week

[2.2.0] Checkmk Werk 16364 created: tag_group: change the identification field from 'ident' to 'id'

by Checkmk werks level 1

Title: tag_group: change the identification field from 'ident' to 'id' Class: fix Compatible: incomp Component: rest-api Date: 1706534034 Edition: cre Level: 1 Version: 2.2.0p22 Before this Werk, when creating a tag group, the ident field was used to provide its identification as well as that of the tags associated to the group, however the information was returned in the id field. This Werk unifies the names and now the ident fields are renamed to id. Users should adapt their scripts accordingly. For comptatibility reasons CheckMK 2.2.0 and 2.3.0 will support both id and ident, but ident will be removed on the next version. The following example shows the changes that need to be applied to the payload to use this endpoint: Original payload: C+: { "ident": "test_group", "title": "Test group", "help_text": "My test groupd", "tags": [ {"ident": "test", "title": "Test Tag"} ] } C-: Updated payload: C+: { "id": "test_group", "title": "Test group", "help_text": "My test groupd", "tags": [ {"id": "test", "title": "Test Tag"} ] } C-:

7 months, 1 week

[2.3.0] Checkmk Werk 16295 adapted: postfix_mailq_status: Rework discovery

by Checkmk werks level 1

Werk 16295 was adapted. The following is the new Werk, a diff is shown at the end of the message. Title: postfix_mailq_status: Rework discovery Class: fix Compatible: compat Component: checks Date: 1700560692 Edition: cre Level: 1 Version: 2.3.0b1 With this werk the postfix status service is not discovered if Postfix is not running. The default mail queue is now discovered as "Postfix Status default". ------------------------------------<diff>------------------------------------------- Title: postfix_mailq_status: Rework discovery Class: fix - Compatible: incomp ? -- + Compatible: compat ? ++ Component: checks Date: 1700560692 Edition: cre Level: 1 Version: 2.3.0b1 With this werk the postfix status service is not discovered if Postfix is not running. The default mail queue is now discovered as "Postfix Status default". - In order to make the check plugin work you have to perform a re-discovery on the affected hosts. - Otherwise, the service "Postfix Status" (dicovered before this change) will stop working. -

7 months, 1 week

[2.4.0] Checkmk Werk 16389 adapted: authentication: remove user profile dir when unknown user and failed to login

by Checkmk werks level 1

Werk 16389 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # authentication: remove user profile dir when unknown user and failed to login key | value ---------- | --- date | 2024-01-26T15:59:51+00:00 version | 2.4.0b1 class | fix edition | cre component | wato level | 1 compatible | yes Previously, failed login attempts with an unknown user would create a user profile directory. This is no longer the case. The profile directory is now only created for valid users. ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) # authentication: remove user profile dir when unknown user and failed to login key | value ---------- | --- date | 2024-01-26T15:59:51+00:00 - version | 2.3.0b1 ? ^ + version | 2.4.0b1 ? ^ class | fix edition | cre component | wato level | 1 compatible | yes Previously, failed login attempts with an unknown user would create a user profile directory. This is no longer the case. The profile directory is now only created for valid users.

7 months, 1 week

[2.4.0] Checkmk Werk 16377 created: postfix_mailq: Rename "Postfix Queue" to "Postfix Queue default"

by Checkmk werks level 1

[//]: # (werk v2) # postfix_mailq: Rename "Postfix Queue" to "Postfix Queue default" key | value ---------- | --- date | 2024-02-01T08:44:18+00:00 version | 2.4.0b1 class | fix edition | cre component | checks level | 1 compatible | yes This affects users monitoring hosts that run one single postfix instance. For new installations, the service "Postfix Queue" will be renamed to "Postfix Queue default". In general, Checkmk is able to monitor multiple postfix instances running on the monitored host. This will change the name in the common case where users are not running multiple postfix instances, but only the "default" one. If you want to switch to the new service description after an upgrade, you can do so using the setting "Use new service descriptions". Be aware that you will lose the historic data in case you do that.

7 months, 1 week

[2.2.0] Checkmk Werk 16390 created: notification_rule: cancel previous notifications now working with custom plugin scripts

by Checkmk werks level 1

Title: notification_rule: cancel previous notifications now working with custom plugin scripts Class: fix Compatible: compat Component: rest-api Date: 1706714129 Edition: cre Level: 1 Version: 2.2.0p22 When creating or updating notification rules, the option to "cancel_previous_notifications" was previously not available when the plugin name selected was a custom plugin script. This werk addresses this issue and now allows for custom plugin scripts when setting the option to cancel.

7 months, 1 week

[2.2.0] Checkmk Werk 16325 created: netapp_ontap_psu: fix discovery ruleset

by Checkmk werks level 1

Title: netapp_ontap_psu: fix discovery ruleset Class: fix Compatible: incomp Component: checks Date: 1706706487 Edition: cre Level: 1 Version: 2.2.0p22 This problem affected users who wanted to discover the 'summary' mode of PSU service: it was not possible to configure the appropriate discovery rule. This werk fixes this behaviour. A rediscovery is required for the change to take effect.

7 months, 1 week

[2.2.0] Checkmk Werk 15324 created: agent_bakery: mk_postgres.py: restore required keys

by Checkmk werks level 1

Title: agent_bakery: mk_postgres.py: restore required keys Class: fix Compatible: compat Component: checks Date: 1706768367 Edition: cre Level: 1 Version: 2.2.0p22 <a href="https://checkmk.com/werk/15645">Werk #15645</a> made the Inputs of "Instance settings" of the Agent rule "PostgreSQL database and sessions (Linux, Windows)" optional by accident. If you did not specify all keys, baking agents failed with a <code>KeyError</code> on the automation call.

7 months, 1 week

[2.2.0] Checkmk Werk 16389 created: authentication: remove user profile dir when unknown user and failed to login

by Checkmk werks level 1

Title: authentication: remove user profile dir when unknown user and failed to login Class: fix Compatible: compat Component: wato Date: 1706284791 Edition: cre Level: 1 Version: 2.2.0p22 Previously, failed login attempts with an unknown user would create a user profile directory. This is no longer the case. The profile directory is now only created for valid users.

7 months, 1 week

[2.2.0] Checkmk Werk 16384 adapted: notification rule: allow for non builtin service levels

by Checkmk werks level 1

Werk 16384 was adapted. The following is the new Werk, a diff is shown at the end of the message. Title: notification rule: allow for non builtin service levels Class: fix Compatible: incomp Component: rest-api Date: 1705490346 Edition: cre Level: 1 Version: 2.2.0p21 When configuring a notification rule via the Rest API, you could not set the value for "match_service_levels" to anything but the default service levels. This werk addresses this issue by now allowing any of the service levels configured to be used. This change mean that there is a change to the request schema. Previously, we accepeted the service level string value, whereas now we accept the integer value. Previous schema ``` {"match_service_levels": { "state": "enabled", "value": {"from_level": "silver", "to_level": "gold"} } } ``` New schema ``` {"match_service_levels: { "state": "enabled", "value": {"from_level": 10, "to_level": 20} } } ``` ------------------------------------<diff>------------------------------------------- Title: notification rule: allow for non builtin service levels Class: fix Compatible: incomp Component: rest-api Date: 1705490346 Edition: cre Level: 1 Version: 2.2.0p21 When configuring a notification rule via the Rest API, you could not set the value for "match_service_levels" to anything but the default service levels. This werk addresses this issue by now allowing any of the service levels configured to be used. This change mean that there is a change to the request schema. Previously, we accepeted the service level string value, whereas now we accept the integer value. Previous schema ``` {"match_service_levels": { "state": "enabled", "value": {"from_level": "silver", "to_level": "gold"} } } ``` New schema ``` {"match_service_levels: { "state": "enabled", - "value": {"from_level" 10, "to_level": 20} + "value": {"from_level": 10, "to_level": 20} ? + } } ```

7 months, 1 week

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 February 2024