Checkmk werks level1 March 2024

checkmk-werks-lvl1@lists.checkmk.com

1 participants
258 discussions

[2.2.0] Checkmk Werk 16240 adapted: Crash on missing thread count on AIX

by Checkmk werks level 1

Werk 16240 was adapted. The following is the new Werk, a diff is shown at the end of the message. Title: Crash on missing thread count on AIX Class: fix Compatible: compat Component: checks Date: 1709129579 Edition: cre Level: 1 Version: 2.2.0p25 You're affected if you want to monitor your CPU and the cpu check crashes with something like: C+: File "/omd/sites/YOURSITE/lib/python3/cmk/base/plugins/agent_based/cpu.py", line 48, in parse_cpu count=int(row[3].split("/")[1]), ValueError (invalid literal for int() with base 10: '') C-: We saw this happening on AIX system when the ps information cannot be obtained due to low memory. The parsing is now more resilient against such missing data. ------------------------------------<diff>------------------------------------------- Title: Crash on missing thread count on AIX Class: fix Compatible: compat Component: checks Date: 1709129579 Edition: cre Level: 1 - Version: 2.2.0p24 ? ^ + Version: 2.2.0p25 ? ^ You're affected if you want to monitor your CPU and the cpu check crashes with something like: C+: File "/omd/sites/YOURSITE/lib/python3/cmk/base/plugins/agent_based/cpu.py", line 48, in parse_cpu count=int(row[3].split("/")[1]), ValueError (invalid literal for int() with base 10: '') C-: We saw this happening on AIX system when the ps information cannot be obtained due to low memory. The parsing is now more resilient against such missing data.

5 months, 4 weeks

[2.2.0] Checkmk Werk 16373 adapted: metrics: allow dots in metric ids

by Checkmk werks level 1

Werk 16373 was adapted. The following is the new Werk, a diff is shown at the end of the message. Title: metrics: allow dots in metric ids Class: fix Compatible: compat Component: rest-api Date: 1709109314 Edition: cre Level: 1 Version: 2.2.0p25 Before this Werk, the REST API was not able to access metrics named after IP addresses. This Werk fixes that and allows user to access metrics containing dots on the id ------------------------------------<diff>------------------------------------------- Title: metrics: allow dots in metric ids Class: fix Compatible: compat Component: rest-api Date: 1709109314 Edition: cre Level: 1 - Version: 2.2.0p24 ? ^ + Version: 2.2.0p25 ? ^ Before this Werk, the REST API was not able to access metrics named after IP addresses. This Werk fixes that and allows user to access metrics containing dots on the id

5 months, 4 weeks

[2.2.0] Checkmk Werk 16239 adapted: Extend devices found by apc_ats_status

by Checkmk werks level 1

Werk 16239 was adapted. The following is the new Werk, a diff is shown at the end of the message. Title: Extend devices found by apc_ats_status Class: fix Compatible: compat Component: checks Date: 1709123851 Edition: cre Level: 1 Version: 2.2.0p25 This werk affects you, in case you try to monitor your APC Rack Automatic Transfer Switch with <tt>apc_ats_status</tt>. Previously some devices were not discovered due to a too strict scan function. Futher, we enable monitoring other power supplies available at such devices as for example 1V and 3.3V. This was fixed now. ------------------------------------<diff>------------------------------------------- Title: Extend devices found by apc_ats_status Class: fix Compatible: compat Component: checks Date: 1709123851 Edition: cre Level: 1 - Version: 2.2.0p24 ? ^ + Version: 2.2.0p25 ? ^ This werk affects you, in case you try to monitor your APC Rack Automatic Transfer Switch with <tt>apc_ats_status</tt>. Previously some devices were not discovered due to a too strict scan function. Futher, we enable monitoring other power supplies available at such devices as for example 1V and 3.3V. This was fixed now.

5 months, 4 weeks

[2.2.0] Checkmk Werk 16175 adapted: apc_netbotz_sensors, apc_netbotz_other_sensors: Add monitoring for Netbotz 50 devices

by Checkmk werks level 1

Werk 16175 was adapted. The following is the new Werk, a diff is shown at the end of the message. Title: apc_netbotz_sensors, apc_netbotz_other_sensors: Add monitoring for Netbotz 50 devices Class: feature Compatible: compat Component: checks Date: 1709894365 Edition: cre Level: 1 Version: 2.2.0p25 apc_netbotz_sensors and apc_netbotz_other_sensors checks provided monitoring for APC Netbotz v2 devices. Now, the checks can additionally monitor APC Netbotz 50 devices. ------------------------------------<diff>------------------------------------------- Title: apc_netbotz_sensors, apc_netbotz_other_sensors: Add monitoring for Netbotz 50 devices Class: feature Compatible: compat Component: checks Date: 1709894365 Edition: cre Level: 1 - Version: 2.2.0p24 ? ^ + Version: 2.2.0p25 ? ^ apc_netbotz_sensors and apc_netbotz_other_sensors checks provided monitoring for APC Netbotz v2 devices. Now, the checks can additionally monitor APC Netbotz 50 devices.

5 months, 4 weeks

[2.2.0] Checkmk Werk 16320 adapted: Publish permission handling

by Checkmk werks level 1

Werk 16320 was adapted. The following is the new Werk, a diff is shown at the end of the message. Title: Publish permission handling Class: fix Compatible: incomp Component: multisite Date: 1709641954 Edition: cre Level: 1 Version: 2.2.0p25 Werk 13498 introduced the possibility to set publish permissions independently of each other. Still, the permission "Publish views" (e.g. for publishing views) was needed to see the published views. This has been fixed. Note: Please check your publish configuration in views, dashboards, etc. ------------------------------------<diff>------------------------------------------- Title: Publish permission handling Class: fix Compatible: incomp Component: multisite Date: 1709641954 Edition: cre Level: 1 - Version: 2.2.0p24 ? ^ + Version: 2.2.0p25 ? ^ Werk 13498 introduced the possibility to set publish permissions independently of each other. Still, the permission "Publish views" (e.g. for publishing views) was needed to see the published views. This has been fixed. Note: Please check your publish configuration in views, dashboards, etc.

5 months, 4 weeks

[2.2.0] Checkmk Werk 16372 adapted: swagger: Fix parameters not working in Swagger

by Checkmk werks level 1

Werk 16372 was adapted. The following is the new Werk, a diff is shown at the end of the message. Title: swagger: Fix parameters not working in Swagger Class: feature Compatible: compat Component: rest-api Date: 1709285249 Edition: cre Level: 1 Version: 2.2.0p25 Since not all Python regexes are ECMA (JavaScript) compliant, several parameter fields did not work in Swagger. This werk solves the problem by adjusting the regexes to be compatible with JavaScript. ------------------------------------<diff>------------------------------------------- Title: swagger: Fix parameters not working in Swagger Class: feature Compatible: compat Component: rest-api Date: 1709285249 Edition: cre Level: 1 - Version: 2.2.0p24 ? ^ + Version: 2.2.0p25 ? ^ Since not all Python regexes are ECMA (JavaScript) compliant, several parameter fields did not work in Swagger. This werk solves the problem by adjusting the regexes to be compatible with JavaScript.

5 months, 4 weeks

[2.2.0] Checkmk Werk 16238 adapted: Add m7i.large as aws resource type

by Checkmk werks level 1

Werk 16238 was adapted. The following is the new Werk, a diff is shown at the end of the message. Title: Add m7i.large as aws resource type Class: feature Compatible: compat Component: checks Date: 1709038229 Edition: cre Level: 1 Version: 2.2.0p25 You're affected if your aws_ec2_limits check reported "Unknown resource" and you're using "m7i.large". The aws resource names are changing from time to time and we will need to find a more stable solution for that in the future. But for now, this will be fixed by adding the resource name "m7i.large" to our internal list of aws resources. ------------------------------------<diff>------------------------------------------- Title: Add m7i.large as aws resource type Class: feature Compatible: compat Component: checks Date: 1709038229 Edition: cre Level: 1 - Version: 2.2.0p24 ? ^ + Version: 2.2.0p25 ? ^ You're affected if your aws_ec2_limits check reported "Unknown resource" and you're using "m7i.large". The aws resource names are changing from time to time and we will need to find a more stable solution for that in the future. But for now, this will be fixed by adding the resource name "m7i.large" to our internal list of aws resources.

5 months, 4 weeks

[2.2.0] Checkmk Werk 16322 adapted: Show used filter of virtual host tree

by Checkmk werks level 1

Werk 16322 was adapted. The following is the new Werk, a diff is shown at the end of the message. Title: Show used filter of virtual host tree Class: fix Compatible: compat Component: multisite Date: 1709905532 Edition: cre Level: 1 Version: 2.2.0p25 If you opened the "Filter" option of a view that was visited via a link from the "Virtual host tree" snapin, all filters were empty. ------------------------------------<diff>------------------------------------------- Title: Show used filter of virtual host tree Class: fix Compatible: compat Component: multisite Date: 1709905532 Edition: cre Level: 1 - Version: 2.2.0p24 ? ^ + Version: 2.2.0p25 ? ^ If you opened the "Filter" option of a view that was visited via a link from the "Virtual host tree" snapin, all filters were empty.

5 months, 4 weeks

[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.

5 months, 4 weeks

[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.

5 months, 4 weeks

← Newer
1
...
4
5
6
7
8
9
10
...
26
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 March 2024