Werk 16114 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: folder_config: Extend GET and DELETE endpoints folder name pattern to match the CREATE enpoint one
Class: fix
Compatible: compat
Component: rest-api
Date: 1696846527
Edition: cre
Level: 1
Version: 2.2.0p25
Prior to this Werk, the folder name pattern for GET and DELETE endpoints did not allow the use of unicode characters while they were supported by the CREATE endpoint, with the result that folders created with such characters could not be accessed or deleted from the REST API.
For example, the user was able to create a folder named û亿Ï8Ĺ, which then could not be read or deleted from the API.
This Werk widens the folder name pattern on GET and DELETE endpoints to align with the CREATE one and now all of them support unicode characters.
------------------------------------<diff>-------------------------------------------
Title: folder_config: Extend GET and DELETE endpoints folder name pattern to match the CREATE enpoint one
Class: fix
Compatible: compat
Component: rest-api
Date: 1696846527
Edition: cre
Level: 1
- Version: 2.2.0p24
? ^
+ Version: 2.2.0p25
? ^
Prior to this Werk, the folder name pattern for GET and DELETE endpoints did not allow the use of unicode characters while they were supported by the CREATE endpoint, with the result that folders created with such characters could not be accessed or deleted from the REST API.
For example, the user was able to create a folder named û亿Ï8Ĺ, which then could not be read or deleted from the API.
This Werk widens the folder name pattern on GET and DELETE endpoints to align with the CREATE one and now all of them support unicode characters.
Werk 16176 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: postfix: Fix Postfix status monitoring for agents run in Docker
Class: fix
Compatible: compat
Component: checks
Date: 1710323821
Edition: cre
Level: 1
Version: 2.2.0p25
Previously, Checkmk agent used the data from /proc to determine if Postfix instance is running.
Since docker containers don't have permissions to read /proc, the agent always reported
the Postfix instance as 'not running'.
This resulted in CRIT 'Postfix status' service even if Postfix instance was running correctly.
------------------------------------<diff>-------------------------------------------
Title: postfix: Fix Postfix status monitoring for agents run in Docker
Class: fix
Compatible: compat
Component: checks
Date: 1710323821
Edition: cre
Level: 1
- Version: 2.2.0p24
? ^
+ Version: 2.2.0p25
? ^
Previously, Checkmk agent used the data from /proc to determine if Postfix instance is running.
Since docker containers don't have permissions to read /proc, the agent always reported
the Postfix instance as 'not running'.
This resulted in CRIT 'Postfix status' service even if Postfix instance was running correctly.
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.
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
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.
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.
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.
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.
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.
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.