Checkmk werks level1 March 2024

checkmk-werks-lvl1@lists.checkmk.com

1 participants
258 discussions

[2.2.0] Checkmk Werk 16372 created: swagger: Fix parameters not working in Swagger

by Checkmk werks level 1

Title: swagger: Fix parameters not working in Swagger Class: feature Compatible: compat Component: rest-api Date: 1709285249 Edition: cre Level: 1 Version: 2.2.0p24 Since not all Python regexes are ECMA (JavaScript) compliant, several parameter fields did not work in Swagger. This werk solves the problem by adjusting the regexes to be compatible with JavaScript.

7 months, 2 weeks

[2.2.0] Checkmk Werk 16373 created: metrics: allow dots in metric ids

by Checkmk werks level 1

Title: metrics: allow dots in metric ids Class: fix Compatible: compat Component: rest-api Date: 1709109314 Edition: cre Level: 1 Version: 2.2.0p24 Before this Werk, the REST API was not able to access metrics named after IP addresses. This Werk fixes that and allows user to access metrics containing dots on the id

7 months, 2 weeks

[2.4.0] Checkmk Werk 16549 created: Agent updates failing on Solaris 10

by Checkmk werks level 1

[//]: # (werk v2) # Agent updates failing on Solaris 10 key | value ---------- | --- date | 2024-03-01T08:43:58+00:00 version | 2.4.0b1 class | fix edition | cee component | agents level | 1 compatible | no On some Solaris 10 systems, an agent update did crash with error message ``` /var/sadm/pkg/check-mk-agent/install/postremove: syntax error at line 19: `(' unexpected pkgrm: ERROR: postremove script did not complete successfully ``` If you ran into this error, to make the update perform again, please delete the file `/var/sadm/pkg/check-mk-agent/install/postremove` on affected systems. Technical background:\ The postremove script used the subshell evaluation syntax `$(...)` that is incompatible to the standard `bin/sh` shell found on some Solaris 10 systems.

7 months, 2 weeks

[2.3.0] Checkmk Werk 16559 created: Host properties: Make "Additional IPv4/6 addresses" depend on "IP address family" attribute

by Checkmk werks level 1

[//]: # (werk v2) # Host properties: Make "Additional IPv4/6 addresses" depend on "IP address family" attribute key | value ---------- | --- date | 2024-03-01T09:06:53+00:00 version | 2.3.0b1 class | fix edition | cre component | wato level | 1 compatible | yes The attributes "IPv4/6 address" are toggled based on the "IP address family" attribute in the host properties dialog. This behavior is now also applied to the "Additional IPv4/6 addresses" attributes.

7 months, 2 weeks

[2.4.0] Checkmk Werk 16241 created: Crash during parsing of systemd unit when description is missing

by Checkmk werks level 1

[//]: # (werk v2) # Crash during parsing of systemd unit when description is missing key | value ---------- | --- date | 2024-02-29T10:20:38+00:00 version | 2.4.0b1 class | fix edition | cre component | checks level | 1 compatible | yes You're affected if you're monitoring your systemd units with an old agent and your unit is missing a descpription. Parsing may have failed with: ``` > loaded_status, active_status, current_state, descr = remains.split(" ", 3) E ValueError: not enough values to unpack (expected 4, got 3) ``` This is fixed now.

7 months, 2 weeks

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

by Checkmk werks level 1

Werk 16364 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # tag_group: change the identification field from 'ident' to 'id' key | value ---------- | --- date | 2024-01-29T13:13:54+00:00 version | 2.4.0b1 class | fix edition | cre component | rest-api level | 1 compatible | no 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: ```json { "ident": "test_group", "title": "Test group", "help_text": "My test groupd", "tags": [ {"ident": "test", "title": "Test Tag"} ] } ``` Updated payload: ```json { "id": "test_group", "title": "Test group", "help_text": "My test groupd", "tags": [ {"id": "test", "title": "Test Tag"} ] } ``` ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) - # swagger: Fix parameters not working in Swagger + # tag_group: change the identification field from 'ident' to 'id' key | value ---------- | --- - date | 2024-02-29T13:52:31+00:00 ? ^ ^^^^ + date | 2024-01-29T13:13:54+00:00 ? ^ +++ ^ version | 2.4.0b1 class | fix edition | cre component | rest-api level | 1 - compatible | yes ? ^^^ + compatible | no ? ^^ - Since not all Python regexes are ECMA (JavaScript) compliant, several parameter fields did not work in Swagger. This werk solves the problem by adjusting the regexes to be compatible with JavaScript. + 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: + ```json + { + "ident": "test_group", + "title": "Test group", + "help_text": "My test groupd", + "tags": [ + {"ident": "test", "title": "Test Tag"} + ] + } + ``` + Updated payload: + ```json + { + "id": "test_group", + "title": "Test group", + "help_text": "My test groupd", + "tags": [ + {"id": "test", "title": "Test Tag"} + ] + } + ``` +

7 months, 2 weeks

[2.4.0] Checkmk Werk 16372 created: swagger: Fix parameters not working in Swagger

by Checkmk werks level 1

[//]: # (werk v2) # swagger: Fix parameters not working in Swagger key | value ---------- | --- date | 2024-03-01T09:27:29+00:00 version | 2.4.0b1 class | feature edition | cre component | rest-api level | 1 compatible | yes Since not all Python regexes are ECMA (JavaScript) compliant, several parameter fields did not work in Swagger. This werk solves the problem by adjusting the regexes to be compatible with JavaScript.

7 months, 2 weeks

[2.4.0] Checkmk Werk 16364 adapted: swagger: Fix parameters not working in Swagger

by Checkmk werks level 1

Werk 16364 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # swagger: Fix parameters not working in Swagger key | value ---------- | --- date | 2024-02-29T13:52:31+00:00 version | 2.4.0b1 class | fix edition | cre component | rest-api level | 1 compatible | yes Since not all Python regexes are ECMA (JavaScript) compliant, several parameter fields did not work in Swagger. This werk solves the problem by adjusting the regexes to be compatible with JavaScript. ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) - # tag_group: change the identification field from 'ident' to 'id' + # swagger: Fix parameters not working in Swagger key | value ---------- | --- - date | 2024-01-29T13:13:54+00:00 ? ^ ---- + date | 2024-02-29T13:52:31+00:00 ? ^ ++++ version | 2.4.0b1 class | fix edition | cre component | rest-api level | 1 - compatible | no ? ^^ + compatible | yes ? ^^^ + Since not all Python regexes are ECMA (JavaScript) compliant, several parameter fields did not work in Swagger. This werk solves the problem by adjusting the regexes to be compatible with JavaScript. - 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: - ```json - { - "ident": "test_group", - "title": "Test group", - "help_text": "My test groupd", - "tags": [ - {"ident": "test", "title": "Test Tag"} - ] - } - ``` - Updated payload: - ```json - { - "id": "test_group", - "title": "Test group", - "help_text": "My test groupd", - "tags": [ - {"id": "test", "title": "Test Tag"} - ] - } - ``` - -

7 months, 2 weeks

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 March 2024