[//]: # (werk v2)
# Handle the uptime of Docker containers across time zones
key | value
---------- | ---
date | 2024-04-12T09:35:03+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
As of version 2.3, the uptime monitoring service for Docker containers could crash if the container's start time was later than the current CheckMk site's current time. This resulted in a negative uptime calculation error (ValueError: "Cannot render negative timespan").
This could occur in situations where the host system and the container had different configured timezones.
We now correctly handle all timestamps, ensuring accurate uptime calculations regardless of timezone configurations.
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.0p26
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.0p25
? ^
+ Version: 2.2.0p26
? ^
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 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.0p26
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.0p25
? ^
+ Version: 2.2.0p26
? ^
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 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.0p26
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.0p25
? ^
+ Version: 2.2.0p26
? ^
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.
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.0p26
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.0p25
? ^
+ Version: 2.2.0p26
? ^
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 16355 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: Graph oject lists: Avoid strange help texts in list views (non-English only)
Class: fix
Compatible: compat
Component: multisite
Date: 1713176416
Edition: cee
Level: 1
Version: 2.2.0p26
When using Checkmk in a language other than English, the list views for graph collections, graph
tunings, custom graphs and forecast graphs might have displayed strange help texts such as
"Project-Id-Version: Checkmk user interface translation 0.1 ...".
This happened only for graph objects with empty descriptions and only if the inline help was
activated for the corresponding page.
------------------------------------<diff>-------------------------------------------
Title: Graph oject lists: Avoid strange help texts in list views (non-English only)
Class: fix
Compatible: compat
Component: multisite
Date: 1713176416
Edition: cee
Level: 1
- Version: 2.2.0p25
? ^
+ Version: 2.2.0p26
? ^
When using Checkmk in a language other than English, the list views for graph collections, graph
tunings, custom graphs and forecast graphs might have displayed strange help texts such as
"Project-Id-Version: Checkmk user interface translation 0.1 ...".
This happened only for graph objects with empty descriptions and only if the inline help was
activated for the corresponding page.
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.0p26
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.0p25
? ^
+ Version: 2.2.0p26
? ^
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 16350 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: Support Diagnostics: The timeout for creating a dump is now configurable
Class: feature
Compatible: compat
Component: wato
Date: 1712920020
Edition: cre
Level: 1
Version: 2.2.0p26
Before this werk, the process of creating a Support Diagnostics Dump sometimes lead to a timeout exception. The hard-coded timeout was 110s.
Now, it's possible to configure the timeout in the user interface.
------------------------------------<diff>-------------------------------------------
Title: Support Diagnostics: The timeout for creating a dump is now configurable
Class: feature
Compatible: compat
Component: wato
Date: 1712920020
Edition: cre
Level: 1
- Version: 2.2.0p25
? ^
+ Version: 2.2.0p26
? ^
Before this werk, the process of creating a Support Diagnostics Dump sometimes lead to a timeout exception. The hard-coded timeout was 110s.
Now, it's possible to configure the timeout in the user interface.
Werk 15841 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: The configuration is correctly loaded by RRD helper processes
Class: fix
Compatible: compat
Component: core
Date: 1711447383
Edition: cee
Level: 2
Version: 2.2.0p26
This change ensures the reloading of the configuration by already
running RRD processes, thereby guaranteeing that those processes are
using the correct configuration.
SUP-17787
CMK-16318
------------------------------------<diff>-------------------------------------------
Title: The configuration is correctly loaded by RRD helper processes
Class: fix
Compatible: compat
Component: core
Date: 1711447383
Edition: cee
Level: 2
- Version: 2.2.0p25
? ^
+ Version: 2.2.0p26
? ^
This change ensures the reloading of the configuration by already
running RRD processes, thereby guaranteeing that those processes are
using the correct configuration.
SUP-17787
CMK-16318
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.0p26
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.0p25
? ^
+ Version: 2.2.0p26
? ^
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.