Checkmk werks level1 September 2024

checkmk-werks-lvl1@lists.checkmk.com

1 participants
124 discussions

[2.4.0] Checkmk Werk 17275 created: Introduce cmk/customer host label

by Checkmk werks level 1

[//]: # (werk v2) # Introduce cmk/customer host label key | value ---------- | --- date | 2024-09-05T13:06:17+00:00 version | 2.4.0b1 class | feature edition | cme component | multisite level | 1 compatible | yes The MSP edition will now create a `cmk/customer` label for each host. This label can be used to configure filters based on customers.

12 hours, 8 minutes

[2.2.0] Checkmk Werk 16123 created: Use the original message text for rewriting the comment field

by Checkmk werks level 1

Title: Use the original message text for rewriting the comment field Class: fix Compatible: compat Component: ec Date: 1726062847 Edition: cre Level: 1 Version: 2.2.0p34 Werk 16534 made the rewriting of the comment field use the comment field itself as the basis. For this field, it doesn't really make sense, because rewriting is the only way to fill that field, so e.g. \0 was always empty. With this change, we revert to the old behaviour where all match groups refer to the original message text.

1 day, 11 hours

[2.3.0] Checkmk Werk 16123 created: Use the original message text for rewriting the comment field

by Checkmk werks level 1

[//]: # (werk v2) # Use the original message text for rewriting the comment field key | value ---------- | --- date | 2024-09-11T13:54:07+00:00 version | 2.3.0p17 class | fix edition | cre component | ec level | 1 compatible | yes Werk 16534 made the rewriting of the comment field use the comment field itself as the basis. For this field, it doesn't really make sense, because rewriting is the only way to fill that field, so e.g. \0 was always empty. With this change, we revert to the old behaviour where all match groups refer to the original message text.

1 day, 11 hours

[2.3.0] Checkmk Werk 16251 deleted: Update monitoring-plugins to 2.4.0

by Checkmk werks level 1

Werk 16251 was deleted. The following Werk is no longer relevant. [//]: # (werk v2) # Update monitoring-plugins to 2.4.0 key | value ---------- | --- date | 2024-09-04T14:11:06+00:00 version | 2.3.0p16 class | feature edition | cre component | checks level | 1 compatible | yes

1 day, 11 hours

[2.3.0] Checkmk Werk 17168 created: Test notifications: Fix simulation of "Start of downtime"

by Checkmk werks level 1

[//]: # (werk v2) # Test notifications: Fix simulation of "Start of downtime" key | value ---------- | --- date | 2024-09-17T05:19:13+00:00 version | 2.3.0p16 class | fix edition | cre component | notifications level | 1 compatible | yes If you used the simulation method "Start of downtime", the test did not match any rule with event type option "Start or end of a scheduled downtime". This has been fixed.

1 day, 12 hours

[2.3.0] Checkmk Werk 17035 created: mysql_replica_slave: Adapt mk_mysql for MySQL version 8.0.22 and above

by Checkmk werks level 1

[//]: # (werk v2) # mysql_replica_slave: Adapt mk_mysql for MySQL version 8.0.22 and above key | value ---------- | --- date | 2024-09-10T12:46:28+00:00 version | 2.3.0p16 class | feature edition | cre component | checks level | 1 compatible | yes From MySQL 8.0.22, SHOW SLAVE STATUS is deprecated and the alias SHOW REPLICA STATUS should be used instead. The statement works in the same way as before, only the terminology used for the statement and its output has changed. For the sake of compatibility, the service name will stay the same 'MySQL Slave'. There is no user intervention required.

1 day, 12 hours

[2.3.0] Checkmk Werk 16251 created: Update monitoring-plugins to 2.4.0

by Checkmk werks level 1

[//]: # (werk v2) # Update monitoring-plugins to 2.4.0 key | value ---------- | --- date | 2024-09-04T14:11:06+00:00 version | 2.3.0p16 class | feature edition | cre component | checks level | 1 compatible | yes

1 day, 12 hours

[2.4.0] Checkmk Werk 17291 created: Make Synthetic Monitoring available on Linux

by Checkmk werks level 1

[//]: # (werk v2) # Make Synthetic Monitoring available on Linux key | value ---------- | --- date | 2024-09-17T11:45:40+00:00 version | 2.4.0b1 class | feature edition | cee component | checks level | 2 compatible | yes Synthethic monitoring is now available for deployment on Linux systems. Previously, only Windows systems were supported. In terms of functionality, there is one difference between Linux and Windows: Testing applications on the Desktop is not supported on Linux systems. All other functionality is available on both systems.

1 day, 12 hours

[2.4.0] Checkmk Werk 17290 created: Synthetic Monitoring: Re-work Keyword Monitoring

by Checkmk werks level 1

[//]: # (werk v2) # Synthetic Monitoring: Re-work Keyword Monitoring key | value ---------- | --- date | 2024-09-17T09:43:05+00:00 version | 2.4.0b1 class | feature edition | cee component | checks level | 2 compatible | no Version 2.3 offered the option to monitor the runtime of Robot Framework (RF) keywords. This was possible via the option _Maximum Keyword runtime_ in the ruleset _Robotmk test_. However, this option was hard to use because the resulting metric names were not robust to modifications of the test definition. Moving, adding or deleting keywords resulted in shifting metric names, which rendered the recorded metric histories hard to interpret. To address this issue, the monitoring of keywords (formerly as an accessory to test monitoring) has been expanded into an independent Key Performance Indicator (KPI) monitoring in version 2.4. The option _Maximum Keyword runtime_ has been removed from the _Robotmk test_ ruleset. Instead, Checkmk now offers two distinct mechanisms for monitoring KPIs: 1. **Pattern-based approach**: There is a new service discovery ruleset called _Robotmk KPI discovery_. This ruleset offers the option to discover keywords based on regular expressions. However, contrary to before, the matched RF keywords must be unique per RF test. Furthermore, each matched keyword now results in a separate service. 2. **Marker-based approach**: To overcome the limitation of unique keywords per RF test, version 2.4 additionally introduces the option to mark RF keywords directly in the test definitions as KPIs to be monitored by Checkmk. To this end, we introduce a [dedicated RF keyword library](https://pypi.org/project/robotframework-robotmklibrary). For now, this library exposes one keyword only, namely `Monitor Subsequent Keyword Runtime`. This keyword marks the subsequent keyword as a KPI that will be monitored with a separate service by Checkmk. Users can optionally specify an identifier for this KPI that will be used in the corresponding service name. This enables monitoring multiple KPIs that are based on the same underlying RF keyword. In both cases, thresholds for the KPI runtime are configurable via the new ruleset _Robotmk KPI monitoring_. These changes are marked as incompatible because no automatic migration from 2.3 to 2.4 is possible. When updating to 2.4, the patterns previously configured below the _Maximum Keyword runtime_ option will be dropped.

1 day, 12 hours

[2.4.0] Checkmk Werk 16123 created: Use the original message text for rewriting the comment field

by Checkmk werks level 1

[//]: # (werk v2) # Use the original message text for rewriting the comment field key | value ---------- | --- date | 2024-09-11T13:54:07+00:00 version | 2.4.0b1 class | fix edition | cre component | ec level | 1 compatible | yes Werk 16534 made the rewriting of the comment field use the comment field itself as the basis. For this field, it doesn't really make sense, because rewriting is the only way to fill that field, so e.g. \0 was always empty. With this change, we revert to the old behaviour where all match groups refer to the original message text.

1 day, 12 hours

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 September 2024