Checkmk werks level1 October 2023

checkmk-werks-lvl1@lists.checkmk.com

1 participants
195 discussions

[2.2.0] Checkmk Werk 16032 created: Crash: Reports with service specific SLA column

by Checkmk werks level 1

Title: Crash: Reports with service specific SLA column Class: fix Compatible: compat Component: reporting Date: 1698060200 Edition: cee Knowledge: doc Level: 1 Version: 2.2.0p13 When generating a report containing the `Hosts/Services: SLA - Service specific` column the generation of the report would crash. Now the report is rendered correctly again.

10 months, 4 weeks

[2.2.0] Checkmk Werk 16156 created: downtimes: site_id only required when deleting downtimes by_id

by Checkmk werks level 1

Title: downtimes: site_id only required when deleting downtimes by_id Class: fix Compatible: incomp Component: rest-api Date: 1697811956 Edition: cre Knowledge: undoc Level: 1 State: unknown Version: 2.2.0p13 We recently introduced a change with werk 15966 which means that the site_id is now required when deleting downtimes via the REST API. However, only the 'by_id' option leaves the downtime selection ambigious, while the options 'params' or 'query' already have the ability to pinpoint the downtimes requested, therefore, the site_id should not be required in these cases. This werk addresses this oversight and introduces a change where the site_id is only required when deleteing by_id.

10 months, 4 weeks

[2.3.0] Checkmk Werk 16032 adapted: Crash: Reports with service specific SLA column

by Checkmk werks level 1

Werk 16032 was adapted. The following is the new Werk, a diff is shown at the end of the message. Title: Crash: Reports with service specific SLA column Class: fix Compatible: compat Component: reporting Date: 1698060200 Edition: cee Level: 1 Version: 2.3.0b1 When generating a report containing the `Hosts/Services: SLA - Service specific` column the generation of the report would crash. Now the report is rendered correctly again. ------------------------------------<diff>------------------------------------------- Title: Crash: Reports with service specific SLA column Class: fix Compatible: compat Component: reporting Date: 1698060200 Edition: cee Level: 1 Version: 2.3.0b1 - When generating a report containing the + When generating a report containing the `Hosts/Services: SLA - Service specific` column + the generation of the report would crash. Now the report is rendered correctly again.

10 months, 4 weeks

[2.3.0] Checkmk Werk 16032 created: Crash: Reports with service specific SLA column

by Checkmk werks level 1

Title: Crash: Reports with service specific SLA column Class: fix Compatible: compat Component: reporting Date: 1698060200 Edition: cee Level: 1 Version: 2.3.0b1 When generating a report containing the Now the report is rendered correctly again.

10 months, 4 weeks

[2.3.0] Checkmk Werk 16062 created: cisco_webex_teams: Fix failed notification on response code 204

by Checkmk werks level 1

Title: cisco_webex_teams: Fix failed notification on response code 204 Class: fix Compatible: compat Component: notifications Date: 1697549543 Edition: cre Level: 1 Version: 2.3.0b1 The notification script produced a failed notification, even if the processing was successful.

10 months, 4 weeks

[2.3.0] Checkmk Werk 15024 created: "+" is now an allowed character in user ids

by Checkmk werks level 1

Title: "+" is now an allowed character in user ids Class: feature Compatible: compat Component: wato Date: 1698053634 Edition: cre Level: 1 Version: 2.3.0b1 "+" has been added as an allowed character in user ids. For example now "user+checkmk(a)company.com" is an allowed user id.

10 months, 4 weeks

[2.3.0] Checkmk Werk 16156 created: downtimes: site_id only required when deleting downtimes by_id

by Checkmk werks level 1

Title: downtimes: site_id only required when deleting downtimes by_id Class: fix Compatible: incomp Component: rest-api Date: 1697811956 Edition: cre Level: 1 Version: 2.3.0b1 We recently introduced a change with werk 15966 which means that the site_id is now required when deleting downtimes via the REST API. However, only the 'by_id' option leaves the downtime selection ambigious, while the options 'params' or 'query' already have the ability to pinpoint the downtimes requested, therefore, the site_id should not be required in these cases. This werk addresses this oversight and introduces a change where the site_id is only required when deleteing by_id.

10 months, 4 weeks

[2.1.0] Checkmk Werk 15872 created: This Werk fixes misbehaved metrics after an upgrade

by Checkmk werks level 1

Title: This Werk fixes misbehaved metrics after an upgrade Class: fix Compatible: compat Component: checks Date: 1697611822 Edition: cre Knowledge: undoc Level: 1 State: unknown Version: 2.1.0p36 After an upgrade various plugins metrics would misbehave, until eventually settling again. More specificly: All averaged metrics would forget the previously recorded values. As a result, the "averaged" metric follows the original one very closely. After a few values are recorded the desired smoothing effect of the averaging will start to show. The time it takes for the metric to stabilise depends on the configured or implemented weights (<i>"Backlog in minutes"</i>).

10 months, 4 weeks

[2.1.0] Checkmk Werk 15875 created: viprinet_router: Fix failing config migration

by Checkmk werks level 1

Title: viprinet_router: Fix failing config migration Class: fix Compatible: compat Component: checks Date: 1698007452 Edition: cre Knowledge: undoc Level: 1 State: unknown Version: 2.1.0p36 Fix failing config migration in environments containing discovered viprinet_router checks.

10 months, 4 weeks

[2.2.0] Checkmk Werk 15872 created: This Werk fixes misbehaved metrics after an upgrade

by Checkmk werks level 1

Title: This Werk fixes misbehaved metrics after an upgrade Class: fix Compatible: compat Component: checks Date: 1697611822 Edition: cre Knowledge: undoc Level: 1 State: unknown Version: 2.2.0p13 After an upgrade various plugins metrics would misbehave, until eventually settling again. More specificly: All averaged metrics would forget the previously recorded values. As a result, the "averaged" metric follows the original one very closely. After a few values are recorded the desired smoothing effect of the averaging will start to show. The time it takes for the metric to stabilise depends on the configured or implemented weights (<i>"Backlog in minutes"</i>).

10 months, 4 weeks

← Newer
1
2
3
4
5
6
7
8
...
20
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 October 2023