Checkmk werks level1

checkmk-werks-lvl1@lists.checkmk.com

1 participants
15873 discussions

[2.2.0] Checkmk Werk 17114 adapted: esx_vsphere_objects: Allow configuration of "Stand by" state

by Checkmk werks level 1

Werk 17114 was adapted. The following is the new Werk, a diff is shown at the end of the message. Title: esx_vsphere_objects: Allow configuration of "Stand by" state Class: fix Compatible: compat Component: checks Date: 1720598913 Edition: cre Level: 1 Version: 2.2.0p32 ------------------------------------<diff>------------------------------------------- Title: esx_vsphere_objects: Allow configuration of "Stand by" state Class: fix Compatible: compat Component: checks Date: 1720598913 Edition: cre Level: 1 - Version: 2.2.0p31 ? ^ + Version: 2.2.0p32 ? ^

2 months, 1 week

[2.2.0] Checkmk Werk 16437 adapted: omd: Improve Runtime with Many Sites

by Checkmk werks level 1

Werk 16437 was adapted. The following is the new Werk, a diff is shown at the end of the message. Title: omd: Improve Runtime with Many Sites Class: fix Compatible: compat Component: omd Date: 1720082692 Edition: cre Level: 2 Version: 2.2.0p32 With this Werk, all invocations of the <tt>omd</tt> command line tool are faster. This Werk should not affect behaviour in any other way. The performance improvements mostly affect hosts, which have a high number of sites. ------------------------------------<diff>------------------------------------------- Title: omd: Improve Runtime with Many Sites Class: fix Compatible: compat Component: omd Date: 1720082692 Edition: cre Level: 2 - Version: 2.2.0p31 ? ^ + Version: 2.2.0p32 ? ^ With this Werk, all invocations of the <tt>omd</tt> command line tool are faster. This Werk should not affect behaviour in any other way. The performance improvements mostly affect hosts, which have a high number of sites.

2 months, 1 week

[2.2.0] Checkmk Werk 16863 adapted: proxmox: Fix log parsing crash for Proxmox versions 3.2.4 and newer

by Checkmk werks level 1

Werk 16863 was adapted. The following is the new Werk, a diff is shown at the end of the message. Title: proxmox: Fix log parsing crash for Proxmox versions 3.2.4 and newer Class: fix Compatible: compat Component: checks Date: 1719585241 Edition: cre Level: 1 Version: 2.2.0p32 The backup log format changed in Proxmox version 3.2.4 which resulted in a crash in the Proxmox special agent. The special agent can now handle both old and the new format of backup log messages. ------------------------------------<diff>------------------------------------------- Title: proxmox: Fix log parsing crash for Proxmox versions 3.2.4 and newer Class: fix Compatible: compat Component: checks Date: 1719585241 Edition: cre Level: 1 - Version: 2.2.0p31 ? ^ + Version: 2.2.0p32 ? ^ The backup log format changed in Proxmox version 3.2.4 which resulted in a crash in the Proxmox special agent. The special agent can now handle both old and the new format of backup log messages.

2 months, 1 week

[2.2.0] Checkmk Werk 17117 adapted: multipath: Allow for dots in the UUID

by Checkmk werks level 1

Werk 17117 was adapted. The following is the new Werk, a diff is shown at the end of the message. Title: multipath: Allow for dots in the UUID Class: fix Compatible: compat Component: checks Date: 1720624648 Edition: cre Level: 1 Version: 2.2.0p32 Previously devices with dots in their UUID have not been discovered. ------------------------------------<diff>------------------------------------------- Title: multipath: Allow for dots in the UUID Class: fix Compatible: compat Component: checks Date: 1720624648 Edition: cre Level: 1 - Version: 2.2.0p31 ? ^ + Version: 2.2.0p32 ? ^ Previously devices with dots in their UUID have not been discovered.

2 months, 1 week

[2.2.0] Checkmk Werk 17074 adapted: msexch_database: Use consistent units (ms/s) in rules & graphs

by Checkmk werks level 1

Werk 17074 was adapted. The following is the new Werk, a diff is shown at the end of the message. Title: msexch_database: Use consistent units (ms/s) in rules & graphs Class: fix Compatible: compat Component: checks Date: 1718695214 Edition: cee Level: 1 Version: 2.2.0p32 The msexch_database reported its values in ms in the summary/ruleset but displayed the same value as seconds in the graph. With this werk, all units will be reported consistently. ------------------------------------<diff>------------------------------------------- Title: msexch_database: Use consistent units (ms/s) in rules & graphs Class: fix Compatible: compat Component: checks Date: 1718695214 Edition: cee Level: 1 - Version: 2.2.0p28 ? - + Version: 2.2.0p32 ? + The msexch_database reported its values in ms in the summary/ruleset but displayed the same value as seconds in the graph. With this werk, all units will be reported consistently.

2 months, 1 week

[2.2.0] Checkmk Werk 17079 created: mk_redis: Autodetect Checkmk instances

by Checkmk werks level 1

Title: mk_redis: Autodetect Checkmk instances Class: fix Compatible: compat Component: checks Date: 1718695661 Edition: cre Level: 1 Version: 2.2.0p31 Previously the redis agent plugin configured to autodetect would not detect the Checkmk redis instances. Now, on hosts running a Checkmk site, these instances can be autodetected as well and monitored as any other redis instance.

2 months, 1 week

[2.3.0] Checkmk Werk 17002 created: Support Azure Databases for MySQL flexible server

by Checkmk werks level 1

[//]: # (werk v2) # Support Azure Databases for MySQL flexible server key | value ---------- | --- date | 2024-07-09T10:09:56+00:00 version | 2.3.0p11 class | feature edition | cre component | checks level | 1 compatible | yes Microsoft is retiring the Azure resource "Database for MySQL single server" (see https://learn.microsoft.com/en-us/azure/mysql/migrate/whats-happening-to-my…). With this Werk we now support monitoring the recommended Azure resource "Database for MySQL flexible server". In the rule "Microsoft Azure" under "Azure services to monitor" users can now select the new option "Database for MySQL flexible server". (Note that the former option "Database for MySQL" was renamed to "Database for MySQL single server" and stays in place.) The metrics monitored for flexible servers correspond to those monitored for single servers and the same checks are used. See the [check plugin catalog](https://checkmk.com/integrations?distributions%5B%5D=check_mk&dist… for more details.

2 months, 1 week

[2.3.0] Checkmk Werk 17079 adapted: mk_redis: Autodetect Checkmk instances

by Checkmk werks level 1

Werk 17079 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # mk_redis: Autodetect Checkmk instances key | value ---------- | --- date | 2024-06-18T07:27:41+00:00 version | 2.3.0p11 class | fix edition | cre component | checks level | 1 compatible | yes Previously the redis agent plugin configured to autodetect would not detect the Checkmk redis instances. Now, on hosts running a Checkmk site, these instances can be autodetected as well and monitored as any other redis instance. ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) # mk_redis: Autodetect Checkmk instances key | value ---------- | --- date | 2024-06-18T07:27:41+00:00 - version | 2.3.0p10 ? ^ + version | 2.3.0p11 ? ^ class | fix edition | cre component | checks level | 1 compatible | yes Previously the redis agent plugin configured to autodetect would not detect the Checkmk redis instances. Now, on hosts running a Checkmk site, these instances can be autodetected as well and monitored as any other redis instance.

2 months, 1 week

[2.3.0] Checkmk Werk 17079 created: mk_redis: Autodetect Checkmk instances

by Checkmk werks level 1

[//]: # (werk v2) # mk_redis: Autodetect Checkmk instances key | value ---------- | --- date | 2024-06-18T07:27:41+00:00 version | 2.3.0p10 class | fix edition | cre component | checks level | 1 compatible | yes Previously the redis agent plugin configured to autodetect would not detect the Checkmk redis instances. Now, on hosts running a Checkmk site, these instances can be autodetected as well and monitored as any other redis instance.

2 months, 1 week

[2.3.0] Checkmk Werk 16431 adapted: omd restore: Fix RuntimeError: Failed to determine site version

by Checkmk werks level 1

Werk 16431 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # omd restore: Fix RuntimeError: Failed to determine site version key | value ---------- | --- compatible | yes version | 2.3.0p11 date | 2024-06-11T12:03:43+00:00 level | 1 class | fix component | omd edition | cre Due to a regression introduced by <a href="https://checkmk.com/werk/16422">Werk #16422</a>, the command `omd restore <NEW_SITE> <ARCHIVE_PATH>` could fail: ``` File "/omd/versions/2.3.0p6.cee/lib/python3/omdlib/main.py", line 3522, in _restore_backup_from_tar old_site.replacements(), ^^^^^^^^^^^^^^^^^^^^^^^ File "/omd/versions/2.3.0p6.cee/lib/python3/omdlib/contexts.py", line 136, in replacements raise RuntimeError("Failed to determine site version") ``` The failure only occured, if the user provided a site name, which differed from the original name, and the original site did no longer exist. This crash also affected the `Migrate existing Site` function of the appliance. If you are affected by this crash, but are unable to update, then you can start be restoring the site without a new name. The site can then be renamed with `omd mv`. ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) # omd restore: Fix RuntimeError: Failed to determine site version key | value ---------- | --- compatible | yes - version | 2.3.0p10 ? ^ + version | 2.3.0p11 ? ^ date | 2024-06-11T12:03:43+00:00 level | 1 class | fix component | omd edition | cre Due to a regression introduced by <a href="https://checkmk.com/werk/16422">Werk #16422</a>, the command `omd restore <NEW_SITE> <ARCHIVE_PATH>` could fail: ``` File "/omd/versions/2.3.0p6.cee/lib/python3/omdlib/main.py", line 3522, in _restore_backup_from_tar old_site.replacements(), ^^^^^^^^^^^^^^^^^^^^^^^ File "/omd/versions/2.3.0p6.cee/lib/python3/omdlib/contexts.py", line 136, in replacements raise RuntimeError("Failed to determine site version") ``` The failure only occured, if the user provided a site name, which differed from the original name, and the original site did no longer exist. This crash also affected the `Migrate existing Site` function of the appliance. If you are affected by this crash, but are unable to update, then you can start be restoring the site without a new name. The site can then be renamed with `omd mv`.

2 months, 1 week

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1