Checkmk werks level1 December 2023

checkmk-werks-lvl1@lists.checkmk.com

1 participants
128 discussions

[2.2.0] Checkmk Werk 16275 created: Crash of Checkmk Agent service if MRPE plugins are used

by Checkmk werks level 1

Title: Crash of Checkmk Agent service if MRPE plugins are used Class: fix Compatible: compat Component: checks Date: 1702646733 Edition: cre Level: 1 Version: 2.2.0p18

8 months, 3 weeks

[2.3.0] Checkmk Werk 16274 created: Unusable services for "HPE Proliant Servers: Raid Status"

by Checkmk werks level 1

Title: Unusable services for "HPE Proliant Servers: Raid Status" Class: fix Compatible: incomp Component: checks Date: 1702636533 Edition: cre Level: 1 Version: 2.3.0b1 This fixes some unusable services of the "HPE Proliant Servers: Raid Status" plugin. This werk only affecs you if you observe unknown "Logical device <ITEM>" services after the upgrade. In case you are affected please run a discovery on the affected hosts and fix the monitoring history as described below. We observed some devices to send <tt>"\x00"</tt> (the null-byte) as their name (OID .1.3.6.1.4.1.232.3.2.3.1.1.14). Not all components delt well with it, leading to unacknowlegable downtimes, non matching rules and the like. We now replace all null-bytes with <tt>"\\x00"</tt> (the literal containing the four characters backslash, 'x', 'zero', 'zero'). As of Checkmk 2.3, this should in fact no longer be necessary, but as we need a backportable solution, we change the item consistently in all versions. If this affects you, you might also want to fix the services in the monitring history by running C+: sed -i 's|\x00|\\x00|' var/check_mk/core/history var/check_mk/core/archive/* C-:

8 months, 3 weeks

[2.3.0] Checkmk Werk 16275 created: Crash of Checkmk Agent service if MRPE plugins are used

by Checkmk werks level 1

Title: Crash of Checkmk Agent service if MRPE plugins are used Class: fix Compatible: compat Component: checks Date: 1702646733 Edition: cre Level: 1 Version: 2.3.0b1

8 months, 3 weeks

[2.1.0] Checkmk Werk 16010 created: Custom graphs/Graph collections: Fix permissions if admin wants to see custom graphs from other users

by Checkmk werks level 1

Title: Custom graphs/Graph collections: Fix permissions if admin wants to see custom graphs from other users Class: fix Compatible: compat Component: multisite Date: 1702027122 Edition: cee Level: 1 Version: 2.1.0p38

8 months, 3 weeks

[2.2.0] Checkmk Werk 16010 created: Custom graphs/Graph collections: Fix permissions if admin wants to see custom graphs from other users

by Checkmk werks level 1

8 months, 3 weeks

[2.3.0] Checkmk Werk 16010 created: Custom graphs/Graph collections: Fix permissions if admin wants to see custom graphs from other users

by Checkmk werks level 1

8 months, 3 weeks

[2.3.0] Checkmk Werk 16358 created: Session termination after maximum session age

by Checkmk werks level 1

Title: Session termination after maximum session age Class: feature Compatible: compat Component: wato Date: 1702467423 Edition: cre Level: 1 Version: 2.3.0b1 To mitigate the risk of a session takeover you can now define a maximum session duration. This is set by default to 24 hours. For the case that somebody is actively using the session over this duration you can also configure a threshold to warn users about the upcoming session termination. This value is set by default to 15 minutes. You can disable this feature completely via the global setting *Session management*.

8 months, 3 weeks

[2.3.0] Checkmk Werk 16207 created: host_tag_group: Fix 500 status code when creating a host_tag_group with id already in use

by Checkmk werks level 1

Title: host_tag_group: Fix 500 status code when creating a host_tag_group with id already in use Class: fix Compatible: compat Component: rest-api Date: 1702550742 Edition: cre Level: 1 Version: 2.3.0b1 Before this Werk, when trying to create a host_tag_group using an id belonging to an aux_tag the endpoint returned a status 500 (Internal Server Error). This Werk fixes that behaviour and now returns a status 400, informing that the id is in use. CMK-15167

8 months, 3 weeks

[2.2.0] Checkmk Werk 15873 created: ucd_cpu_load: Consider the number of CPUs

by Checkmk werks level 1

Title: ucd_cpu_load: Consider the number of CPUs Class: fix Compatible: compat Component: checks Date: 1697635673 Edition: cre Level: 1 Version: 2.2.0p18 The number of CPUs in UCD SNMP Daemon: CPU Utilization was hardcoded to 1, which is mostly wrong today. With this Werk we count the number of CPUs by fetching {HOST-RESOURCES-V2-MIB::hrProcessorFrwID}. If this is not available the check falls back to 1 CPU.

8 months, 4 weeks

[2.1.0] Checkmk Werk 13478 adapted: Mitigate wrong conversion of disabled service rules on update

by Checkmk werks level 1

Werk 13478 was adapted. The following is the new Werk, a diff is shown at the end of the message. Title: Mitigate wrong conversion of disabled service rules on update Class: fix Compatible: incomp Component: wato Date: 1639747685 Edition: cre Knowledge: doc Level: 1 State: unknown Version: 2.1.0b1 During <tt>cmk-update-config</tt> some disabled services rules are being broken by introducing an undesired escaping. This werk reduces the number of cases in which this happens. Users "Disabled Services" rules were affected if they fullfilled all of the following criteria: <ul> <li>They have exactly one host condition (explicit or pattern)</li> <li>They have no tag based conditions</li> <li>All their patterns for the service name end in "<tt>$</tt>"</li> </ul> After this werk, only rules will be affected if they additionally <ul> <li> have exactly one explicit host condition (not a regular expression)</li> <li> contain both quoted and unquoted special characters in their service name pattern</li> </ul> For instance: "<tt>Foo[12]$</tt>" and "<tt>Foo\[12\]$</tt>" will remain unchanged, whereas "<tt>Foo\[1\][2]$</tt>" will be changed to "<tt>Foo\[1\]\[2\]$</tt>". If this still affects you, you can avoid meeting the above criteria. For instance try to replace "<tt>my_hostname</tt>" by "<tt>~^my_hostname$</tt>" or to craft a service name pattern that does not require the trailing "<tt>$</tt>". ------------------------------------<diff>------------------------------------------- Title: Mitigate wrong conversion of disabled service rules on update Class: fix Compatible: incomp Component: wato Date: 1639747685 Edition: cre Knowledge: doc Level: 1 State: unknown Version: 2.1.0b1 During <tt>cmk-update-config</tt> some disabled services rules are being broken by introducing an undesired escaping. This werk reduces the number of cases in which this happens. Users "Disabled Services" rules were affected if they fullfilled all of the following criteria: <ul> <li>They have exactly one host condition (explicit or pattern)</li> <li>They have no tag based conditions</li> <li>All their patterns for the service name end in "<tt>$</tt>"</li> </ul> After this werk, only rules will be affected if they additionally <ul> <li> have exactly one explicit host condition (not a regular expression)</li> - <li> contain both quoted and unquoted special characters</li> in their service name pattern ? ----- + <li> contain both quoted and unquoted special characters in their service name pattern</li> ? +++++ </ul> For instance: "<tt>Foo[12]$</tt>" and "<tt>Foo\[12\]$</tt>" will remain unchanged, whereas "<tt>Foo\[1\][2]$</tt>" will be changed to "<tt>Foo\[1\]\[2\]$</tt>". If this still affects you, you can avoid meeting the above criteria. For instance try to replace "<tt>my_hostname</tt>" by "<tt>~^my_hostname$</tt>" or to craft a service name pattern that does not require the trailing "<tt>$</tt>". -

8 months, 4 weeks

← Newer
1
2
3
4
5
6
7
...
13
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 December 2023