Checkmk werks level1

checkmk-werks-lvl1@lists.checkmk.com

1 participants
15940 discussions

[2.3.0] Checkmk Werk 16127 deleted: agent-updater change behaviour of trust-cert option

by Checkmk werks level 1

Werk 16127 was deleted. The following Werk is no longer relevant. Title: agent-updater change behaviour of trust-cert option Class: fix Compatible: compat Component: agents Date: 1695817306 Edition: cee Knowledge: doc Level: 1 Version: 2.3.0b1 When registering the agent-updater and using the <tt>--trust-cert</tt> option the agent-updater used to traverse the certificate-chain and trust the first self-signed certificate in the chain which is usually a CA. Unfortunately this relied on the server to provide the full certificate chain. It is not uncommon to only provide the certificate and the corresponding intermediate CA certificate. In these scenarios the agent-updater failed to trust the certificate. Also the help text indicates that only the server certificate is trusted. With this Werk the agent-updater retrieves the certificate of the server and trusts just that certificate. Caution: If your registration workflow relies on an initial registration with <tt>--trust-cert</tt> option and you don't provide a certificate via another channel (see https://docs.checkmk.com/latest/en/agent_deployment.html#provide_certificat…), you'll now lose trust when changing the Checkmk server's server certificate. If your workflow relies on the <tt>--trust-cert</tt> option, please make sure to provide a valid certificate via the agent updater ruleset or via global settings.

11 months, 1 week

[2.3.0] Checkmk Werk 16127 created: agent-updater change behaviour of trust-cert option

by Checkmk werks level 1

Title: agent-updater change behaviour of trust-cert option Class: fix Compatible: compat Component: agents Date: 1695817306 Edition: cee Knowledge: doc Level: 1 Version: 2.3.0b1 When registering the agent-updater and using the <tt>--trust-cert</tt> option the agent-updater used to traverse the certificate-chain and trust the first self-signed certificate in the chain which is usually a CA. Unfortunately this relied on the server to provide the full certificate chain. It is not uncommon to only provide the certificate and the corresponding intermediate CA certificate. In these scenarios the agent-updater failed to trust the certificate. Also the help text indicates that only the server certificate is trusted. With this Werk the agent-updater retrieves the certificate of the server and trusts just that certificate. Caution: If your registration workflow relies on an initial registration with <tt>--trust-cert</tt> option and you don't provide a certificate via another channel (see https://docs.checkmk.com/latest/en/agent_deployment.html#provide_certificat…), you'll now lose trust when changing the Checkmk server's server certificate. If your workflow relies on the <tt>--trust-cert</tt> option, please make sure to provide a valid certificate via the agent updater ruleset or via global settings.

11 months, 1 week

[2.2.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 Knowledge: undoc Level: 1 State: unknown Version: 2.2.0p13 The notification script produced a failed notification, even if the processing was successful.

11 months, 1 week

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

11 months, 1 week

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

11 months, 1 week

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

11 months, 1 week

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

11 months, 1 week

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

11 months, 1 week

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

11 months, 1 week

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

11 months, 1 week

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1