Checkmk werks level1 November 2023

checkmk-werks-lvl1@lists.checkmk.com

1 participants
219 discussions

[2.2.0] Checkmk Werk 16192 adapted: Licensing: Distributed monitoring overview during update

by Checkmk werks level 1

Werk 16192 was adapted. The following is the new Werk, a diff is shown at the end of the message. Title: Licensing: Distributed monitoring overview during update Class: fix Compatible: compat Component: multisite Date: 1699368840 Edition: cre Knowledge: doc Level: 1 Version: 2.2.0p14 When updating a distributed setup from version 2.1, the site status on the Distributed Monitoring page will display the error <tt>"<lambda>() got an unexpected keyword argument 'license_state'"</tt> if the remote site has already been updated to version 2.2, but the central site is still version 2.1. The site status will now display correctly. ------------------------------------<diff>------------------------------------------- Title: Licensing: Distributed monitoring overview during update Class: fix Compatible: compat Component: multisite Date: 1699368840 Edition: cre Knowledge: doc Level: 1 - Version: 2.2.0p15 ? ^ + Version: 2.2.0p14 ? ^ When updating a distributed setup from version 2.1, the site status on the Distributed Monitoring page will display the error <tt>"<lambda>() got an unexpected keyword argument 'license_state'"</tt> if the remote site has already been updated to version 2.2, but the central site is still version 2.1. The site status will now display correctly.

10 months, 1 week

[2.2.0] Checkmk Werk 16215 adapted: agent_elasticsearch: resolve error when requesting indices stats

by Checkmk werks level 1

Werk 16215 was adapted. The following is the new Werk, a diff is shown at the end of the message. Title: agent_elasticsearch: resolve error when requesting indices stats Class: fix Compatible: compat Component: checks Date: 1699277518 Edition: cre Knowledge: undoc Level: 1 State: unknown Version: 2.2.0p14 There is a special error case which arises when trying to request the indices stats from Elasticsearch which has at least one alias pointing to a closed index. In the previous version, the special agent completely failed in such scenarios. This werk resolves this by requesting only the accessible indices. ------------------------------------<diff>------------------------------------------- Title: agent_elasticsearch: resolve error when requesting indices stats Class: fix Compatible: compat Component: checks Date: 1699277518 Edition: cre Knowledge: undoc Level: 1 State: unknown - Version: 2.2.0p15 ? ^ + Version: 2.2.0p14 ? ^ There is a special error case which arises when trying to request the indices stats from Elasticsearch which has at least one alias pointing to a closed index. In the previous version, the special agent completely failed in such scenarios. This werk resolves this by requesting only the accessible indices.

10 months, 1 week

[2.2.0] Checkmk Werk 16192 created: Licensing: Distributed monitoring overview during update

by Checkmk werks level 1

Title: Licensing: Distributed monitoring overview during update Class: fix Compatible: compat Component: multisite Date: 1699368840 Edition: cre Knowledge: doc Level: 1 Version: 2.2.0p15 When updating a distributed setup from version 2.1, the site status on the Distributed Monitoring page will display the error <tt>"<lambda>() got an unexpected keyword argument 'license_state'"</tt> if the remote site has already been updated to version 2.2, but the central site is still version 2.1. The site status will now display correctly.

10 months, 1 week

[2.3.0] Checkmk Werk 16293 created: cisco_ucs_mem: check for memory faults

by Checkmk werks level 1

Title: cisco_ucs_mem: check for memory faults Class: feature Compatible: compat Component: checks Date: 1700038826 Edition: cre Level: 1 Version: 2.3.0b1 As of this werk, the plugin additionally checks and reports memory faults reported by the device. Acknowledged faults will be reported as OK. Otherwise, the monitoring state depends on the fault severity: "major" and "critical" are reported as CRITICAL, "warning" and "minor" as WARNING and "cleared" and "info" as OK.

10 months, 1 week

[2.3.0] Checkmk Werk 16216 created: Resolve Runas section in Checkmk Linux agent

by Checkmk werks level 1

Title: Resolve Runas section in Checkmk Linux agent Class: fix Compatible: compat Component: checks Date: 1699515827 Edition: cre Level: 1 Version: 2.3.0b1 Prior to this werk, the Runas section of the Checkmk agent contained a wrong trailing slash which resulted in an error with the find command. As a direct consequence, some or potentially all Runas rules were inadvertently ignored, leading to the plugin, not intended for root, being executed with root privileges. This werk fixes this behaviour.

10 months, 1 week

[2.3.0] Checkmk Werk 16144 created: Ignore piggybacked host names starting with a period

by Checkmk werks level 1

Title: Ignore piggybacked host names starting with a period Class: fix Compatible: incomp Component: core Date: 1699602114 Edition: cre Level: 1 Version: 2.3.0b1 We now skip piggybacked data for hosts names starting with a period. Examples of such invalid names are ".", ".hostname", and ".hostname.domain.com". Users must rename such hosts if they should remain in the monitoring.

10 months, 1 week

[2.3.0] Checkmk Werk 16259 created: Changed local override mechanism for Checkmk plugins

by Checkmk werks level 1

Title: Changed local override mechanism for Checkmk plugins Class: feature Compatible: incomp Component: checks Date: 1700031909 Edition: cre Level: 1 Version: 2.3.0b1 This Werk affects users that have modified existing plugins shipped with Checkmk (or intend to do so in the future). Other plugins are not affected by this change. In Checkmk, users can "hide" shipped plugin files by putting a corresponding file with the same path in the sites <tt>local/</tt> folder. Checkmk will always prefer the files found there over the shipped ones, allowing users to effectively "patch" a sites plugins. While this mechanism probably will continue to work (maybe), it is discouraged and no longer supported. Users that want to modify, replace or extend an existing plugin are advised to make a copy of the plugin, give it a new name and disable the shipped one in the Setup. We believe this step is necessary in order to provide a good user experience for plugin developers and a smooth upgrade process for plugin users. These are the main reasons: <ul> <li> While the APIs for plugin development deliberately do not care about the files names the plugins are in, the current mechanism works based on a file name. This effectively makes the file name part of the APIs. Strictly speaking, moving a plugin to a different file (or splitting large files up) would require an incompatible Werk, as it might break users local overrides. This was mostly not done in the past, and is not sustainable in the future. (Also the Werk only alerts users to the problem, they would still have to deal with it). </li> <li> In the wake of new APIs for plugin development (corresponding Werks will follow), plugins will be moved to new locations in the filesystem a lot, exacerbating the above problem. </li> <li> One of the advantages of the future APIs will be that plugins are bundled by their topic (e.g. all plugins related to Kubernetes might be found in <tt>cmk/plugins/kube</tt>, be it special agents, WATO rulespecs, check plugins or graph definitions). As a result, some changes to the plugin loading mechanism have to be made, resulting in hard to predict results if combined with the above shadowing mechanism. </li> </ul>

10 months, 1 week

[2.3.0] Checkmk Werk 16219 created: Limit length of Hostname

by Checkmk werks level 1

Title: Limit length of Hostname Class: security Compatible: compat Component: wato Date: 1699601325 Edition: cre Level: 1 Version: 2.3.0b1 Prior to this Werk it was possible to create Hosts with arbitrary length. Since Checkmk stores information in files which paths contain the hostname these path could exceed the allowed length leading to various errors to an extend that rendered the usage of parts of the GUI useless. We found this vulnerability internally. Affected Versions: LI: 2.2.0 LI: 2.1.0 LI: 2.0.0 Vulnerability Management: We have rated the issue with a CVSS Score of 2.7 (Low) with the following CVSS vector: <tt>CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L</tt>. We assigned CVE-2023-23549 to this vulnerability. Changes: This Werk adds a maximum length of 253 characters for the hostname.

10 months, 1 week

[2.3.0] Checkmk Werk 16288 created: audit log: Add options to hide object and object type

by Checkmk werks level 1

Title: audit log: Add options to hide object and object type Class: feature Compatible: compat Component: wato Date: 1699875661 Edition: cre Level: 1 Version: 2.3.0b1 This werk introduces the option to toggle the 'object' and 'object type' columns in the audit log table.

10 months, 1 week

[2.3.0] Checkmk Werk 16145 deleted: "Always up" hosts can always notify

by Checkmk werks level 1

Werk 16145 was deleted. The following Werk is no longer relevant. Title: "Always up" hosts can always notify Class: fix Compatible: compat Component: core Date: 1699884551 Edition: cee Level: 1 Version: 2.3.0b1 Do not postpone notifications for "always up" hosts. The notification logic would wrongly assume that "always up" hosts may, in fact, be down and erroneously postpone notifications. This has been fixed, such hosts are never down.

10 months, 1 week

← Newer
1
...
14
15
16
17
18
19
20
21
22
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 November 2023