Checkmk werks level1

checkmk-werks-lvl1@lists.checkmk.com

1 participants
15873 discussions

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

by Checkmk werks level 1

Title: omd: Improve Runtime with Many Sites Class: fix Compatible: compat Component: omd Date: 1720082692 Edition: cre Level: 2 Version: 2.2.0p31 With this Werk, the 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 should largely affect hosts, which have a high number of sites.

2 months, 2 weeks

[2.2.0] Checkmk Werk 16533 adapted: Event Console fix regex match in rule text

by Checkmk werks level 1

Werk 16533 was adapted. The following is the new Werk, a diff is shown at the end of the message. Title: Event Console fix regex match in rule text Class: fix Compatible: compat Component: ec Date: 1719847864 Edition: cee Level: 1 Version: 2.2.0p31 Event console method compile_matching_value had a typo which caused a valid regex to not match, because it was sent as a string SUP-19224 ------------------------------------<diff>------------------------------------------- Title: Event Console fix regex match in rule text Class: fix Compatible: compat Component: ec Date: 1719847864 Edition: cee Level: 1 - Version: 2.2.0p30 ? ^ + Version: 2.2.0p31 ? ^ Event console method compile_matching_value had a typo which caused a valid regex to not match, because it was sent as a string SUP-19224

2 months, 2 weeks

[2.2.0] Checkmk Werk 16999 adapted: Service check commands exclamation mark is no more escaped

by Checkmk werks level 1

Werk 16999 was adapted. The following is the new Werk, a diff is shown at the end of the message. Title: Service check commands exclamation mark is no more escaped Class: fix Compatible: compat Component: multisite Date: 1717399158 Edition: cre Level: 1 Version: 2.2.0p31 Previously instead of "!" the GUI displayed "!" when rendering a service check command. This is fixed to rendering unescaped service check commands to the GUI. ------------------------------------<diff>------------------------------------------- Title: Service check commands exclamation mark is no more escaped Class: fix Compatible: compat Component: multisite Date: 1717399158 Edition: cre Level: 1 - Version: 2.2.0p30 ? ^ + Version: 2.2.0p31 ? ^ Previously instead of "!" the GUI displayed "!" when rendering a service check command. This is fixed to rendering unescaped service check commands to the GUI.

2 months, 2 weeks

[2.2.0] Checkmk Werk 16753 adapted: HW/SW Inventory: Fix missing joined service columns if a service is assigned to a cluster

by Checkmk werks level 1

Werk 16753 was adapted. The following is the new Werk, a diff is shown at the end of the message. Title: HW/SW Inventory: Fix missing joined service columns if a service is assigned to a cluster Class: fix Compatible: compat Component: multisite Date: 1719844378 Edition: cre Level: 1 Version: 2.2.0p31 ------------------------------------<diff>------------------------------------------- Title: HW/SW Inventory: Fix missing joined service columns if a service is assigned to a cluster Class: fix Compatible: compat Component: multisite Date: 1719844378 Edition: cre Level: 1 - Version: 2.2.0p30 ? ^ + Version: 2.2.0p31 ? ^

2 months, 2 weeks

[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.0p31 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.0p30 ? ^ + Version: 2.2.0p31 ? ^ 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, 2 weeks

[2.2.0] Checkmk Werk 17092 created: Fix missing CSRF token issues

by Checkmk werks level 1

Title: Fix missing CSRF token issues Class: fix Compatible: compat Component: wato Date: 1719997630 Edition: cre Level: 1 Version: 2.2.0p30 Werk #17090 in Checkmk 2.3.0p8 and 2.2.0p29 introduced additional CSRF token checks in the GUI. This caused some buttons to not work anymore because the CSRF token was missing, including, but likely not limited to: LI: "Synchronize users" in Setup > Users to manually trigger the LDAP sync (the background sync still runs) LI: "Show analysis" and "Show bulks" in Setup > Events > Notifications LI: Reordering notification rules via drag-and-drop in the same view LI: "Bake agents" in the agent bakery (as a workaround, use "Bake and sign agents") LI: "Acknowledge last baking result" when a bake job failed (as a workaround, delete the failed job instead) This Werk fixes the issues by adding the token.

2 months, 2 weeks

[2.3.0] Checkmk Werk 16436 adapted: kube_pod_conditions: Support PodReadyToStartContainers Condition

by Checkmk werks level 1

Werk 16436 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # kube_pod_conditions: Support PodReadyToStartContainers Condition key | value ---------- | --- date | 2024-07-01T14:21:43+00:00 version | 2.3.0p10 class | feature edition | cre component | checks level | 1 compatible | yes As of Kubernetes version 1.28, the PodCondition `PodHasNetwork` was renamed to `PodReadyToStartContainers`. With this Werk, both naming conventions are supported. This Werk also tweaks the summary of the check to be more consistent across different Kubernetes environments. ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) # kube_pod_conditions: Support PodReadyToStartContainers Condition key | value ---------- | --- date | 2024-07-01T14:21:43+00:00 - version | 2.3.0p9 ? ^ + version | 2.3.0p10 ? ^^ class | feature edition | cre component | checks level | 1 compatible | yes As of Kubernetes version 1.28, the PodCondition `PodHasNetwork` was renamed to `PodReadyToStartContainers`. With this Werk, both naming conventions are supported. This Werk also tweaks the summary of the check to be more consistent across different Kubernetes environments.

2 months, 2 weeks

[2.3.0] Checkmk Werk 16436 created: kube_pod_conditions: Support PodReadyToStartContainers Condition

by Checkmk werks level 1

[//]: # (werk v2) # kube_pod_conditions: Support PodReadyToStartContainers Condition key | value ---------- | --- date | 2024-07-01T14:21:43+00:00 version | 2.3.0p9 class | feature edition | cre component | checks level | 1 compatible | yes As of Kubernetes version 1.28, the PodCondition `PodHasNetwork` was renamed to `PodReadyToStartContainers`. With this Werk, both naming conventions are supported. This Werk also tweaks the summary of the check to be more consistent across different Kubernetes environments.

2 months, 2 weeks

[2.3.0] Checkmk Werk 16589 adapted: Monitor Redfish compatible management boards / BMCs via optional MKP

by Checkmk werks level 1

Werk 16589 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # Monitor Redfish compatible management boards / BMCs via optional MKP key | value ---------- | --- date | 2024-03-06T16:44:06+00:00 version | 2.3.0b3 class | feature edition | cre component | checks level | 1 compatible | yes You can now monitor _Redfish_ compatible management boards / BMCs with Checkmk. To do so, please enable the natively shipped MKP redfish in _Setup --> Extension packages_ (in commercial editions of Checkmk) or via the command line tool `mkp` (in Checkmk Raw). This will enable a new datasource program under _Setup --> Other integrations --> Redfish Compatible Management Controller_. This is an experimental integration created and supported by the Checkmk community (Andreas Döhler/Yogibaer75), which has already been tested in many environments. However, due to the diverse nature of server hardware, we plan to integrate it entirely for Checkmk 2.4.0, once we have gathered further feedback. You can find the latest versions of the extensions in [Andreas' GitHub repository](https://github.com/Yogibaer75/Check_MK-Things/tree/master/check…. There you can also raise issues or raise pull requests until the plug-ins will be mainlined into Checkmk. ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) # Monitor Redfish compatible management boards / BMCs via optional MKP key | value ---------- | --- date | 2024-03-06T16:44:06+00:00 version | 2.3.0b3 class | feature edition | cre component | checks level | 1 compatible | yes You can now monitor _Redfish_ compatible management boards / BMCs with Checkmk. To do so, please enable the natively shipped MKP redfish in _Setup --> Extension packages_ (in commercial editions of Checkmk) or via the command line tool `mkp` (in Checkmk Raw). This will enable a new datasource program under _Setup --> Other integrations --> Redfish Compatible Management Controller_. - This is an experimental integration created by the Checkmk community (Andreas Döhler from Bechtle), which has already been tested in many environments. ? ^^ ^^^^^^^^^^ + This is an experimental integration created and supported by the Checkmk community (Andreas Döhler/Yogibaer75), which has already been tested in many environments. ? ++++++++++++++ ^^^^^^^^ ^^ However, due to the diverse nature of server hardware, we plan to integrate it entirely for Checkmk 2.4.0, once we have gathered further feedback. + You can find the latest versions of the extensions in [Andreas' GitHub repository](https://github.com/Yogibaer75/Check_MK-Things/tree/master/check…. There you can also raise issues or raise pull requests until the plug-ins will be mainlined into Checkmk. +

2 months, 2 weeks

[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.0p10 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.0p9 ? ^ + version | 2.3.0p10 ? ^^ 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, 2 weeks

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1