Checkmk werks level1 January 2024

checkmk-werks-lvl1@lists.checkmk.com

1 participants
231 discussions

[2.1.0] Checkmk Werk 16376 created: DCD: Not respecting "Validity of missing data" setting

by Checkmk werks level 1

Title: DCD: Not respecting "Validity of missing data" setting Class: fix Compatible: compat Component: checks Date: 1706018703 Edition: cre Level: 1 Version: 2.1.0p39 This fixes disappearing hosts in case of temporarily missing data around the time when a cleanup background job is run (around midnight). In case a piggybacked host temporarily did not receive any data while the background (cron) job `cmk --cleanup-piggyback` was executed, a subsequent run of the DCD would not respect the "Validity of missing data" setting, wrongly removing the affected host from the monitoring configuration.

3 months, 2 weeks

[2.2.0] Checkmk Werk 14222 created: BI configuration: Changed element order of "restrict severity to at worst"

by Checkmk werks level 1

Title: BI configuration: Changed element order of "restrict severity to at worst" Class: feature Compatible: compat Component: bi Date: 1706694900 Edition: cre Level: 1 Version: 2.2.0p22 This werk only introduces a visual fix, so no functional changes. The order of the dropdown choice elements did not reflect the severity of the states. The correct severity order for the BI is OK->WARN->UNKNOWN->CRIT, which differs from the order of the monitoring states OK->WARN->CRIT->UNKNOWN.

3 months, 2 weeks

[2.2.0] Checkmk Werk 16376 created: DCD: Not respecting "Validity of missing data" setting

by Checkmk werks level 1

Title: DCD: Not respecting "Validity of missing data" setting Class: fix Compatible: compat Component: checks Date: 1706018703 Edition: cre Level: 1 Version: 2.2.0p22 This fixes disappearing hosts in case of temporarily missing data around the time when a cleanup background job is run (around midnight). In case a piggybacked host temporarily did not receive any data while the background (cron) job <code>cmk --cleanup-piggyback</code> was executed, a subsequent run of the DCD would not respect the "Validity of missing data" setting, wrongly removing the affected host from the monitoring configuration.

3 months, 2 weeks

[2.2.0] Checkmk Werk 15322 created: BGP Peer State Mapping: add connect state

by Checkmk werks level 1

Title: BGP Peer State Mapping: add connect state Class: fix Compatible: compat Component: checks Date: 1706620148 Edition: cre Level: 1 Version: 2.2.0p22 BGP Peer States can be in "connect". This state was missing in checkmk and thus the service was in "UNKNOWN" state.

3 months, 2 weeks

[2.2.0] Checkmk Werk 16387 created: notification_rules: custom plugins now created correctly when using the REST-API

by Checkmk werks level 1

Title: notification_rules: custom plugins now created correctly when using the REST-API Class: fix Compatible: compat Component: rest-api Date: 1705911511 Edition: cre Level: 1 Version: 2.2.0p22 Previous to this werk, when creating a notification rule with a custom plugin via the rest-api, the parameters were not being shown in the UI as expected. The reason being, an incorrect format being saved to file. This werk addresses this issue by correcting the format being saved to file.

3 months, 2 weeks

[2.4.0] Checkmk Werk 14222 created: BI configuration: Changed element order of "restrict severity to at worst"

by Checkmk werks level 1

[//]: # (werk v2) # BI configuration: Changed element order of "restrict severity to at worst" key | value ---------- | --- compatible | yes version | 2.4.0b1 date | 2024-01-31T09:55:00+00:00 level | 1 class | feature component | bi edition | cre This werk only introduces a visual fix, so no functional changes. The order of the dropdown choice elements did not reflect the severity of the states. The correct severity order for the BI is OK->WARN->UNKNOWN->CRIT, which differs from the order of the monitoring states OK->WARN->CRIT->UNKNOWN.

3 months, 2 weeks

[2.4.0] Checkmk Werk 14221 created: Parent/Child topology: No longer ignoring additionally configured filters

by Checkmk werks level 1

[//]: # (werk v2) # Parent/Child topology: No longer ignoring additionally configured filters key | value ---------- | --- date | 2024-01-30T14:11:43+00:00 version | 2.4.0b1 class | fix edition | cre component | multisite level | 1 compatible | yes

3 months, 2 weeks

[2.4.0] Checkmk Werk 16040 created: Add Top list dashlet

by Checkmk werks level 1

[//]: # (werk v2) # Add Top list dashlet key | value ---------- | --- date | 2024-01-31T07:14:24+00:00 version | 2.4.0b1 class | feature edition | cee component | multisite level | 1 compatible | yes The Top list dashlet displays the top (or bottom) X values of a selected metric. The number of values can be selected, but is limited to 50 values.

3 months, 2 weeks

[2.4.0] Checkmk Werk 16376 created: DCD: Not respecting "Validity of missing data" setting

by Checkmk werks level 1

[//]: # (werk v2) # DCD: Not respecting "Validity of missing data" setting key | value ---------- | --- compatible | yes version | 2.4.0b1 date | 2024-01-23T14:05:03+00:00 level | 1 class | fix component | checks edition | cre This fixes disappearing hosts in case of temporarily missing data around the time when a cleanup background job is run (around midnight). In case a piggybacked host temporarily did not receive any data while the background (cron) job <code>cmk --cleanup-piggyback</code> was executed, a subsequent run of the DCD would not respect the "Validity of missing data" setting, wrongly removing the affected host from the monitoring configuration.

3 months, 2 weeks

[2.4.0] Checkmk Werk 14620 created: Sets deprecation age for mails sent by check_mail_loop from 24h to 2h

by Checkmk werks level 1

[//]: # (werk v2) # Sets deprecation age for mails sent by check_mail_loop from 24h to 2h key | value ---------- | --- date | 2024-01-30T12:49:59+00:00 version | 2.4.0b1 class | feature edition | cre component | checks level | 1 compatible | yes Mails sent by `check_mail_loop` had been deprecated only after 24h, which potentially resulted in thousands of mails in circumstances when sent mails could not be processed for whatever reasons. This change lowers this age to 2h resulting in 'only' 120 mails (for this active check being executed every minute).

3 months, 2 weeks

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 January 2024