Checkmk werks level1 April 2024

checkmk-werks-lvl1@lists.checkmk.com

1 participants
306 discussions

[2.4.0] Checkmk Werk 16697 created: Ignore empty "Multiple sites" filter if "Site" filter is set

by Checkmk werks level 1

[//]: # (werk v2) # Ignore empty "Multiple sites" filter if "Site" filter is set key | value ---------- | --- compatible | yes version | 2.4.0b1 date | 2024-04-23T06:07:04+00:00 level | 1 class | fix component | multisite edition | cre If both filters "Multiple sites" and "Sites" were set, the "Multiple sites" filter was used, even if empty.

4 months, 3 weeks

[2.4.0] Checkmk Werk 16802 created: Synthetic monitoring: Fix crash in "Robotmk scheduler (Windows)" bakery rule when attempting to save with invalid settings

by Checkmk werks level 1

[//]: # (werk v2) # Synthetic monitoring: Fix crash in "Robotmk scheduler (Windows)" bakery rule when attempting to save with invalid settings key | value ---------- | --- date | 2024-04-24T12:38:16+00:00 version | 2.4.0b1 class | fix edition | cee component | setup level | 1 compatible | yes When attempting to save the bakery rule "Robotmk scheduler (Windows)" with invalid settings such as an empty base directory or an invalid application name, the UI page crashed with <code>TypeError: argument of type 'NoneType' is not iterable</code>.

4 months, 3 weeks

[2.4.0] Checkmk Werk 16554 created: df: Wrong handling of lower levels for free space

by Checkmk werks level 1

[//]: # (werk v2) # df: Wrong handling of lower levels for free space key | value ---------- | --- compatible | yes version | 2.4.0b1 date | 2024-04-19T12:35:12+00:00 level | 1 class | fix component | checks edition | cre This is a regression since Checkmk 2.2.0. When configuring the Service Monitoring Rule "Filesystems (used space and growth)", configured levels for free space were evaluated incorrectly. As a result, affected services erroneously showed up as *CRIT*. This happened because of a wrong rounding while evaluating the levels, and only affected small filesystems with a size below 1MB.

4 months, 3 weeks

[2.4.0] Checkmk Werk 16804 created: Printer cartridge levels: Allow to configure receptacles and containers individually

by Checkmk werks level 1

[//]: # (werk v2) # Printer cartridge levels: Allow to configure receptacles and containers individually key | value ---------- | --- date | 2024-04-22T09:37:09+00:00 version | 2.4.0b1 class | feature edition | cre component | checks level | 1 compatible | yes Some printers only report "some remaining" in case the exact percentage of the filing level is unknown. For these cases user could explicitly configure the monitoring state. This state can now be configured depending on whether the supply is a container or a receptacle.

4 months, 3 weeks

[2.4.0] Checkmk Werk 14230 created: BI: Fixed incorrect aggregation of downtimes

by Checkmk werks level 1

[//]: # (werk v2) # BI: Fixed incorrect aggregation of downtimes key | value ---------- | --- date | 2024-04-10T12:05:48+00:00 version | 2.4.0b1 class | fix edition | cre component | bi level | 1 compatible | yes The configuration option <tt>Escalate downtimes based on aggregated WARN state</tt> did not correctly since version 1.5. The behaviour is now fixed and works like its mentioned in our [official documentation](https://docs.checkmk.com/latest/en/bi.html#_tuning_options)

4 months, 3 weeks

[2.4.0] Checkmk Werk 14229 created: Valuespecs: Fixed confusion of values when ListOf contains another ListOf and all have the same magic

by Checkmk werks level 1

[//]: # (werk v2) # Valuespecs: Fixed confusion of values when ListOf contains another ListOf and all have the same magic key | value ---------- | --- date | 2024-04-10T09:56:58+00:00 version | 2.4.0b1 class | fix edition | cre component | wato level | 1 compatible | yes Normally, ListOf elements embedded in other ListOf elements should contain a different magic value, otherwise errors will occur when processing forms. This werk here allows the use of identical magic values.

4 months, 3 weeks

[2.4.0] Checkmk Werk 16692 created: inventory_primekey: do not crash upon empty node ID

by Checkmk werks level 1

[//]: # (werk v2) # inventory_primekey: do not crash upon empty node ID key | value ---------- | --- date | 2024-04-20T10:06:26+00:00 version | 2.4.0b1 class | fix edition | cre component | checks level | 1 compatible | yes

4 months, 3 weeks

[2.4.0] Checkmk Werk 15845 created: winperf_if check correctly discovers and processes interfaces with spaces

by Checkmk werks level 1

[//]: # (werk v2) # winperf_if check correctly discovers and processes interfaces with spaces key | value ---------- | --- date | 2024-04-22T15:31:08+00:00 version | 2.4.0b1 class | fix edition | cee component | checks level | 1 compatible | no Previously, some Windows network interface names with additional spaces — particularly before the hash symbol — were not recognized by the check engine. This led to the absence of some services, especially Windows teaming network interfaces. In this release, such interface names are handled correctly thus fixing the problem. Still, you may need to rediscover services again.

4 months, 3 weeks

[2.2.0] Checkmk Werk 16735 created: Fix unknown METRIC element if combined graph is added to dashboard

by Checkmk werks level 1

Title: Fix unknown METRIC element if combined graph is added to dashboard Class: fix Compatible: compat Component: multisite Date: 1713789249 Edition: cee Level: 1 Version: 2.2.0p26

4 months, 3 weeks

[2.2.0] Checkmk Werk 16697 created: Ignore empty "Multiple sites" filter if "Site" filter is set

by Checkmk werks level 1

Title: Ignore empty "Multiple sites" filter if "Site" filter is set Class: fix Compatible: compat Component: multisite Date: 1713852424 Edition: cre Level: 1 Version: 2.2.0p26 If both filters "Multiple sites" and "Sites" were set, the "Multiple sites" filter was used, even if empty.

4 months, 3 weeks

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

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 April 2024