Checkmk werks level1

checkmk-werks-lvl1@lists.checkmk.com

1 participants
15940 discussions

[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 ("Backlog in minutes").

11 months, 1 week

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

11 months, 1 week

[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 ("Backlog in minutes").

11 months, 1 week

[2.2.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.2.0p13 Fix failing config migration in environments containing discovered viprinet_router checks.

11 months, 1 week

[2.2.0] Checkmk Werk 15100 created: re-use of context in multiple threads in activate changes

by Checkmk werks level 1

Title: re-use of context in multiple threads in activate changes Class: fix Compatible: compat Component: core Date: 1697705777 Edition: cre Knowledge: doc Level: 1 Version: 2.2.0p13 When running "activate changes", a "context" object is created and passed to multiple threads. The concurrent use of this context is not supported and can lead to crashes. As a fix, now every thread receives their own copy of the context leading to complete isolation of the threads. No further action is required to activate the fix.

11 months, 1 week

[2.3.0] Checkmk Werk 16187 created: Restrict the group name pattern to disallow incompatible names

by Checkmk werks level 1

Title: Restrict the group name pattern to disallow incompatible names Class: fix Compatible: compat Component: wato Date: 1697196846 Edition: cre Level: 1 Version: 2.3.0b1 Before this werk it was possible to create groups with names that could not be accessed from the REST API. This werk restricts the group name pattern and prevents the creation of incompatible groups names like '.' and '..' from both WATO and the REST API.

11 months, 1 week

[2.3.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 Level: 1 Version: 2.3.0b1 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 ("Backlog in minutes").

11 months, 1 week

[2.3.0] Checkmk Werk 16186 created: Correct the response schemes in audit log endpoints

by Checkmk werks level 1

Title: Correct the response schemes in audit log endpoints Class: fix Compatible: compat Component: rest-api Date: 1697026334 Edition: cre Knowledge: doc Level: 1 Version: 2.3.0b1 This werk removes the 'link' attributes from the response schema as these endpoints do not provide such information.

11 months, 1 week

[2.3.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 Level: 1 Version: 2.3.0b1 Fix failing config migration in environments containing discovered viprinet_router checks.

11 months, 1 week

[2.2.0] Checkmk Werk 16136 adapted: api-docs: include explanation of the special character * for the If-Match header

by Checkmk werks level 1

Werk 16136 was adapted. The following is the new Werk, a diff is shown at the end of the message. Title: api-docs: include explanation of the special character * for the If-Match header Class: fix Compatible: compat Component: rest-api Date: 1695723736 Edition: cre Knowledge: doc Level: 1 State: unknown Version: 2.2.0p11 Most PUT requests to the REST API require an If-Match header containing an ETag. With this Werk we make it possible to provide "*" instead of an ETag, like this: "If-Match": "*" This Werk also adds a short explanation to the REST API documentation. See the section "Updating values" for more information. ------------------------------------<diff>------------------------------------------- Title: api-docs: include explanation of the special character * for the If-Match header Class: fix Compatible: compat Component: rest-api Date: 1695723736 Edition: cre Knowledge: doc Level: 1 State: unknown Version: 2.2.0p11 - We recently made changes to make it possible to provide the following header - in rest-api requests - "If-Match": "*" + Most PUT requests to the REST API require an If-Match header containing + an ETag. With this Werk we make it possible to provide "*" instead of an + ETag, like this: "If-Match": "*" - instead of providing a resource's ETag. + This Werk also adds a short explanation to the REST API documentation. + See the section "Updating values" for more information. - This werk adds a short explanation to the api-docs so that our users know - that this is possible. - - -

11 months, 2 weeks

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1