Checkmk werks level1 September 2024

checkmk-werks-lvl1@lists.checkmk.com

1 participants
124 discussions

[2.3.0] Checkmk Werk 16893 adapted: pure_storage_fa_volumes: protocol_endpoints result in DivisionByZero exception

by Checkmk werks level 1

Werk 16893 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # pure_storage_fa_volumes: protocol_endpoints result in DivisionByZero exception key | value ---------- | --- date | 2024-09-10T12:53:22+00:00 version | 2.3.0p17 class | fix edition | cre component | checks level | 1 compatible | yes Running `pure_storage_fa_volumes` on a `protocol_endpoints` entry resulted in a DivisionByZero exception being thrown due to `total_provisioned` being 0. This change makes `pure_storage_fa_volumes` skip `protocol_endpoint` entirely ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) # pure_storage_fa_volumes: protocol_endpoints result in DivisionByZero exception key | value ---------- | --- date | 2024-09-10T12:53:22+00:00 - version | 2.3.0p16 ? ^ + version | 2.3.0p17 ? ^ class | fix edition | cre component | checks level | 1 compatible | yes Running `pure_storage_fa_volumes` on a `protocol_endpoints` entry resulted in a DivisionByZero exception being thrown due to `total_provisioned` being 0. This change makes `pure_storage_fa_volumes` skip `protocol_endpoint` entirely

12 hours, 7 minutes

[2.3.0] Checkmk Werk 16252 adapted: Reduce API requests during gcp list-assets

by Checkmk werks level 1

Werk 16252 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # Reduce API requests during gcp list-assets key | value ---------- | --- date | 2024-09-10T12:07:04+00:00 version | 2.3.0p17 class | fix edition | cre component | checks level | 1 compatible | yes This werk is relevant to you if you've been monitoring gcp assets and experienced exceeded quota torwards the google API. The special agent will now only acquire data which is really processed by the check plugin which will reduce the requests torwards gcp. ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) # Reduce API requests during gcp list-assets key | value ---------- | --- date | 2024-09-10T12:07:04+00:00 - version | 2.3.0p16 ? ^ + version | 2.3.0p17 ? ^ class | fix edition | cre component | checks level | 1 compatible | yes This werk is relevant to you if you've been monitoring gcp assets and experienced exceeded quota torwards the google API. The special agent will now only acquire data which is really processed by the check plugin which will reduce the requests torwards gcp.

12 hours, 7 minutes

[2.3.0] Checkmk Werk 16122 adapted: Fixed site matching for expected regular event console messages

by Checkmk werks level 1

Werk 16122 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # Fixed site matching for expected regular event console messages key | value ---------- | --- date | 2024-09-11T10:57:26+00:00 version | 2.3.0p17 class | fix edition | cre component | ec level | 1 compatible | yes Due to a regression in 2.2.0, the "Match site" option had no effect for expected regular messages, i.e. it was effectively ignored in that case. This has been fixed. ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) # Fixed site matching for expected regular event console messages key | value ---------- | --- date | 2024-09-11T10:57:26+00:00 - version | 2.3.0p16 ? ^ + version | 2.3.0p17 ? ^ class | fix edition | cre component | ec level | 1 compatible | yes Due to a regression in 2.2.0, the "Match site" option had no effect for expected regular messages, i.e. it was effectively ignored in that case. This has been fixed.

12 hours, 7 minutes

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

by Checkmk werks level 1

Werk 17168 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # Test notifications: Fix simulation of "Start of downtime" key | value ---------- | --- date | 2024-09-17T05:19:13+00:00 version | 2.3.0p17 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. ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) # Test notifications: Fix simulation of "Start of downtime" key | value ---------- | --- date | 2024-09-17T05:19:13+00:00 - version | 2.3.0p16 ? ^ + version | 2.3.0p17 ? ^ 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.

12 hours, 7 minutes

[2.3.0] Checkmk Werk 17033 adapted: if_fortigate: Show admin state in summary

by Checkmk werks level 1

Werk 17033 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # if_fortigate: Show admin state in summary key | value ---------- | --- date | 2024-09-05T13:44:50+00:00 version | 2.3.0p17 class | feature edition | cre component | checks level | 1 compatible | yes With this werk the admin state of the devices will be shown in the summary. ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) # if_fortigate: Show admin state in summary key | value ---------- | --- date | 2024-09-05T13:44:50+00:00 - version | 2.3.0p16 ? ^ + version | 2.3.0p17 ? ^ class | feature edition | cre component | checks level | 1 compatible | yes With this werk the admin state of the devices will be shown in the summary.

12 hours, 7 minutes

[2.3.0] Checkmk Werk 16846 adapted: WATO configures correctly custom imstances for MS SQL Server plugin

by Checkmk werks level 1

Werk 16846 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # WATO configures correctly custom imstances for MS SQL Server plugin key | value ---------- | --- date | 2024-07-19T11:09:57+00:00 version | 2.3.0p17 class | fix edition | cee component | checks level | 2 compatible | yes Previously, configuring custom instances, WATO used wrong names: `conn` instead of a correct `connection` and `auth` instead of a correct `authentication`. With this release the problem has been eliminated, If you are using custom instances you need to bake and deploy new agent package ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) # WATO configures correctly custom imstances for MS SQL Server plugin key | value ---------- | --- date | 2024-07-19T11:09:57+00:00 - version | 2.3.0p16 ? ^ + version | 2.3.0p17 ? ^ class | fix edition | cee component | checks level | 2 compatible | yes Previously, configuring custom instances, WATO used wrong names: `conn` instead of a correct `connection` and `auth` instead of a correct `authentication`. With this release the problem has been eliminated, If you are using custom instances you need to bake and deploy new agent package

12 hours, 7 minutes

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

12 hours, 7 minutes

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

12 hours, 7 minutes

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

12 hours, 7 minutes

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

12 hours, 8 minutes

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 September 2024