Checkmk werks level1 September 2024

checkmk-werks-lvl1@lists.checkmk.com

1 participants
218 discussions

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

by Checkmk werks level 1

Werk 17035 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (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.0p17 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. ------------------------------------<diff>------------------------------------------- [//]: # (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 ? ^ + version | 2.3.0p17 ? ^ 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 month, 3 weeks

[2.3.0] Checkmk Werk 16869 adapted: azure: Don't fetch vNet gateway peerings from another subscription

by Checkmk werks level 1

Werk 16869 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # azure: Don't fetch vNet gateway peerings from another subscription key | value ---------- | --- date | 2024-09-06T15:15:56+00:00 version | 2.3.0p17 class | fix edition | cre component | checks level | 1 compatible | yes Previously, the Azure agent would crash when monitoring vNet gateways which have peerings from a different subscription. The agent wouldn't report the crash and the consequence was that the affected vNet gateway wasn't monitored. Now, the agent will not monitor vNet gateways peerings from another subscription. ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) # azure: Don't fetch vNet gateway peerings from another subscription key | value ---------- | --- date | 2024-09-06T15:15:56+00:00 - version | 2.3.0p16 ? ^ + version | 2.3.0p17 ? ^ class | fix edition | cre component | checks level | 1 compatible | yes Previously, the Azure agent would crash when monitoring vNet gateways which have peerings from a different subscription. The agent wouldn't report the crash and the consequence was that the affected vNet gateway wasn't monitored. Now, the agent will not monitor vNet gateways peerings from another subscription.

1 month, 3 weeks

[2.3.0] Checkmk Werk 17265 adapted: Git: Support long commit messages

by Checkmk werks level 1

Werk 17265 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # Git: Support long commit messages key | value ---------- | --- date | 2024-09-02T10:27:11+00:00 version | 2.3.0p17 class | fix edition | cre component | wato level | 1 compatible | yes When the Git integration was enabled, creating thousands of hosts could result in a crash. This was caused by a limit of the command line. This werk improves the Git integration to support longer messages. ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) # Git: Support long commit messages key | value ---------- | --- date | 2024-09-02T10:27:11+00:00 - version | 2.3.0p16 ? ^ + version | 2.3.0p17 ? ^ class | fix edition | cre component | wato level | 1 compatible | yes When the Git integration was enabled, creating thousands of hosts could result in a crash. This was caused by a limit of the command line. This werk improves the Git integration to support longer messages.

1 month, 3 weeks

[2.4.0] Checkmk Werk 16871 created: smart: Monitor SATA disks connected via HBA

by Checkmk werks level 1

[//]: # (werk v2) # smart: Monitor SATA disks connected via HBA key | value ---------- | --- compatible | yes version | 2.4.0b1 date | 2024-09-17T12:53:40+00:00 level | 1 class | fix component | checks edition | cre Previously, SATA disks connected via HBA weren't monitored by the smart agent plugin. Now, they are monitored the same way as other ATA disks.

1 month, 3 weeks

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

1 month, 3 weeks

[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 month, 3 weeks

[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 month, 3 weeks

[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 month, 3 weeks

[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 month, 3 weeks

[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 month, 3 weeks

← Newer
1
...
9
10
11
12
13
14
15
...
22
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 September 2024