Checkmk werks level1

checkmk-werks-lvl1@lists.checkmk.com

1 participants
15912 discussions

[2.2.0] Checkmk Werk 16404 adapted: omd cp: Fix etc/ssl/agents/legacy_ca.pem Points to Source of Copy

by Checkmk werks level 1

Werk 16404 was adapted. The following is the new Werk, a diff is shown at the end of the message. Title: omd cp: Fix etc/ssl/agents/legacy_ca.pem Points to Source of Copy Class: fix Compatible: compat Component: omd Date: 1707904094 Edition: cre Level: 1 Version: 2.2.0p25 Since Checkmk 2.2.0 there is a agent CA located in <code>etc/ssl/agents/</code>. This CA is different from the site CA. In particular, if updating from 2.1.0 to 2.2.0, Checkmk will create a symlink <code>etc/ssl/agents/legacy_ca.pem</code>, which points to <code>etc/ssl/ca.pem</code>. After performing an <code>omd cp</code>. This symlink would still point to the site, which was the source of the copy. The symlink is now relative. If the site was created with version 2.2.0 or above no symlink is needed. ------------------------------------<diff>------------------------------------------- Title: omd cp: Fix etc/ssl/agents/legacy_ca.pem Points to Source of Copy Class: fix Compatible: compat Component: omd Date: 1707904094 Edition: cre Level: 1 - Version: 2.2.0p24 ? ^ + Version: 2.2.0p25 ? ^ Since Checkmk 2.2.0 there is a agent CA located in <code>etc/ssl/agents/</code>. This CA is different from the site CA. In particular, if updating from 2.1.0 to 2.2.0, Checkmk will create a symlink <code>etc/ssl/agents/legacy_ca.pem</code>, which points to <code>etc/ssl/ca.pem</code>. After performing an <code>omd cp</code>. This symlink would still point to the site, which was the source of the copy. The symlink is now relative. If the site was created with version 2.2.0 or above no symlink is needed.

6 months, 1 week

[2.2.0] Checkmk Werk 16174 adapted: mongodb_replica_set: Fix replication lag and last replication time

by Checkmk werks level 1

Werk 16174 was adapted. The following is the new Werk, a diff is shown at the end of the message. Title: mongodb_replica_set: Fix replication lag and last replication time Class: fix Compatible: compat Component: checks Date: 1709804918 Edition: cre Level: 1 Version: 2.2.0p25 Checkmk previously assumed that timestamps collected from MongoDB oplog are provided in ms. This wasn't the case, which led to wrong values for replication lag and last replication time being shown in the 'MongoDB Replication Lag' service. ------------------------------------<diff>------------------------------------------- Title: mongodb_replica_set: Fix replication lag and last replication time Class: fix Compatible: compat Component: checks Date: 1709804918 Edition: cre Level: 1 - Version: 2.2.0p24 ? ^ + Version: 2.2.0p25 ? ^ Checkmk previously assumed that timestamps collected from MongoDB oplog are provided in ms. This wasn't the case, which led to wrong values for replication lag and last replication time being shown in the 'MongoDB Replication Lag' service.

6 months, 1 week

[2.2.0] Checkmk Werk 16319 adapted: Reduce context/search filter for "Metrics graph of a single service"

by Checkmk werks level 1

Werk 16319 was adapted. The following is the new Werk, a diff is shown at the end of the message. Title: Reduce context/search filter for "Metrics graph of a single service" Class: fix Compatible: incomp Component: reporting Date: 1709025058 Edition: cee Level: 1 Version: 2.2.0p25 Since 2.2 the content element "Metrics graph of a single service" allowed to configure multiple context/search filters. This was wrong because this element is limited to e specific host and service. This change should have no effect on your configuration but we recommend to check reports with such content elements. ------------------------------------<diff>------------------------------------------- Title: Reduce context/search filter for "Metrics graph of a single service" Class: fix Compatible: incomp Component: reporting Date: 1709025058 Edition: cee Level: 1 - Version: 2.2.0p24 ? ^ + Version: 2.2.0p25 ? ^ Since 2.2 the content element "Metrics graph of a single service" allowed to configure multiple context/search filters. This was wrong because this element is limited to e specific host and service. This change should have no effect on your configuration but we recommend to check reports with such content elements.

6 months, 1 week

[2.2.0] Checkmk Werk 15321 adapted: Fix "State if specific check plugins receive no monitoring data" of Rule "Status of the Checkmk service"

by Checkmk werks level 1

Werk 15321 was adapted. The following is the new Werk, a diff is shown at the end of the message. Title: Fix "State if specific check plugins receive no monitoring data" of Rule "Status of the Checkmk service" Class: fix Compatible: compat Component: checks Date: 1706532543 Edition: cre Level: 1 Version: 2.2.0p25 Rule "Status of the Checkmk service" provides a setting called "State if specific check plugins receive no monitoring data" where you can specify a regular expression to match specific check plugins, and assign a status for the "Check_MK" service if this check plugins receives no data. The feature did work correctly if you specified a Status worse than "WARN". But the "Check_MK" service went to "WARN" even if there was an rule to set the status to "OK" if the specific section did not receive any data. This is fixed now. ------------------------------------<diff>------------------------------------------- Title: Fix "State if specific check plugins receive no monitoring data" of Rule "Status of the Checkmk service" Class: fix Compatible: compat Component: checks Date: 1706532543 Edition: cre Level: 1 - Version: 2.2.0p24 ? ^ + Version: 2.2.0p25 ? ^ Rule "Status of the Checkmk service" provides a setting called "State if specific check plugins receive no monitoring data" where you can specify a regular expression to match specific check plugins, and assign a status for the "Check_MK" service if this check plugins receives no data. The feature did work correctly if you specified a Status worse than "WARN". But the "Check_MK" service went to "WARN" even if there was an rule to set the status to "OK" if the specific section did not receive any data. This is fixed now.

6 months, 1 week

[2.2.0] Checkmk Werk 16321 adapted: Fix metric history painter with inherit time range option

by Checkmk werks level 1

Werk 16321 was adapted. The following is the new Werk, a diff is shown at the end of the message. Title: Fix metric history painter with inherit time range option Class: fix Compatible: compat Component: reporting Date: 1709800537 Edition: cee Level: 1 Version: 2.2.0p25 If you used the option “Inherit from report time range” for the painter "Metric history" in report content elements, an error was shown in the report. This affected all previous 2.2 versions. ------------------------------------<diff>------------------------------------------- Title: Fix metric history painter with inherit time range option Class: fix Compatible: compat Component: reporting Date: 1709800537 Edition: cee Level: 1 - Version: 2.2.0p24 ? ^ + Version: 2.2.0p25 ? ^ If you used the option “Inherit from report time range” for the painter "Metric history" in report content elements, an error was shown in the report. This affected all previous 2.2 versions.

6 months, 1 week

[2.2.0] Checkmk Werk 16379 adapted: Allow disabling of bulk walks on inline SNMPv3 hosts

by Checkmk werks level 1

Werk 16379 was adapted. The following is the new Werk, a diff is shown at the end of the message. Title: Allow disabling of bulk walks on inline SNMPv3 hosts Class: fix Compatible: compat Component: checks Date: 1710141228 Edition: cre Level: 1 Version: 2.2.0p25 It was impossible to disable bulkwalks for SNMP version 3 hosts using the inline SNMP backend. It is fixed now in the sense that it works as in the classic backend: In order to disable bulkwalks for SNMP version 3 hosts, you need to make sure they do not match the ruleset "Enable SNMPv2c and bulkwalk for host". A more thorough fix for this bug and the related phrasing in the rulesets is implemented in for Checkmk 2.3, but it was too risky to port into the stable releases. See <a href="https://checkmk.com/werk/16382">Werk #16382</a> for more on that. ------------------------------------<diff>------------------------------------------- Title: Allow disabling of bulk walks on inline SNMPv3 hosts Class: fix Compatible: compat Component: checks Date: 1710141228 Edition: cre Level: 1 - Version: 2.2.0p24 ? ^ + Version: 2.2.0p25 ? ^ It was impossible to disable bulkwalks for SNMP version 3 hosts using the inline SNMP backend. It is fixed now in the sense that it works as in the classic backend: In order to disable bulkwalks for SNMP version 3 hosts, you need to make sure they do not match the ruleset "Enable SNMPv2c and bulkwalk for host". A more thorough fix for this bug and the related phrasing in the rulesets is implemented in for Checkmk 2.3, but it was too risky to port into the stable releases. See <a href="https://checkmk.com/werk/16382">Werk #16382</a> for more on that.

6 months, 1 week

[2.2.0] Checkmk Werk 16484 adapted: Crash when creating combined graphs with empty time filter

by Checkmk werks level 1

Werk 16484 was adapted. The following is the new Werk, a diff is shown at the end of the message. Title: Crash when creating combined graphs with empty time filter Class: fix Compatible: compat Component: multisite Date: 1709884230 Edition: cre Level: 1 Version: 2.2.0p25 When creating a combined graph with an empty time filter (e.g. Last service check), the creation of the combined graph would crash. This behavior is not consistent with the view filtering behavior, where the filter is not applied if it is empty. Now the filter is not applied to combined graphs either. ------------------------------------<diff>------------------------------------------- Title: Crash when creating combined graphs with empty time filter Class: fix Compatible: compat Component: multisite Date: 1709884230 Edition: cre Level: 1 - Version: 2.2.0p24 ? ^ + Version: 2.2.0p25 ? ^ When creating a combined graph with an empty time filter (e.g. Last service check), the creation of the combined graph would crash. This behavior is not consistent with the view filtering behavior, where the filter is not applied if it is empty. Now the filter is not applied to combined graphs either.

6 months, 1 week

[2.2.0] Checkmk Werk 15487 adapted: Fix indentation of tree of folders snapin

by Checkmk werks level 1

Werk 15487 was adapted. The following is the new Werk, a diff is shown at the end of the message. Title: Fix indentation of tree of folders snapin Class: fix Compatible: compat Component: multisite Date: 1683124911 Edition: cre Level: 1 Version: 2.2.0p25 ------------------------------------<diff>------------------------------------------- Title: Fix indentation of tree of folders snapin Class: fix Compatible: compat Component: multisite Date: 1683124911 Edition: cre Level: 1 - Version: 2.2.0p24 ? ^ + Version: 2.2.0p25 ? ^

6 months, 1 week

[2.2.0] Checkmk Werk 16455 adapted: Fix metric scaling of 'rta' for Nagios plugin integration 'check_ping'

by Checkmk werks level 1

Werk 16455 was adapted. The following is the new Werk, a diff is shown at the end of the message. Title: Fix metric scaling of 'rta' for Nagios plugin integration 'check_ping' Class: fix Compatible: compat Component: multisite Date: 1709824147 Edition: cre Level: 1 Version: 2.2.0p25 ------------------------------------<diff>------------------------------------------- Title: Fix metric scaling of 'rta' for Nagios plugin integration 'check_ping' Class: fix Compatible: compat Component: multisite Date: 1709824147 Edition: cre Level: 1 - Version: 2.2.0p24 ? ^ + Version: 2.2.0p25 ? ^

6 months, 1 week

[2.2.0] Checkmk Werk 16456 adapted: Fix licensing recording and verification due to missing instance IDs on remote sites

by Checkmk werks level 1

Werk 16456 was adapted. The following is the new Werk, a diff is shown at the end of the message. Title: Fix licensing recording and verification due to missing instance IDs on remote sites Class: fix Compatible: compat Component: omd Date: 1710148230 Edition: cme Level: 1 Version: 2.2.0p25 This situation can be fixed by stopping and starting remote sites via 'omd stop' and 'omd start', ------------------------------------<diff>------------------------------------------- Title: Fix licensing recording and verification due to missing instance IDs on remote sites Class: fix Compatible: compat Component: omd Date: 1710148230 Edition: cme Level: 1 - Version: 2.2.0p24 ? ^ + Version: 2.2.0p25 ? ^ This situation can be fixed by stopping and starting remote sites via 'omd stop' and 'omd start',

6 months, 1 week

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1