[//]: # (werk v2)
# Container: Support setting custom timezone
key | value
---------- | ---
date | 2024-08-21T15:44:20+00:00
version | 2.4.0b1
class | feature
edition | cre
component | packages
level | 1
compatible | yes
The checkmk containers now support setting the TZ variable for a container to specify what timezone the site should use.
The timezone information is then set for the site running inside the container.
This removes the need to mount timezone files from the host machine into a docker container.
[//]: # (werk v2)
# chrony: change default warning level
key | value
---------- | ---
date | 2024-08-19T06:14:01+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | no
Chrony's default `minpoll` and `maxpoll` values are 64 seconds and 1024 seconds.
In standard situations (good internet connection, low error etc)
the interval between polls should stick near the max value (1024 seconds).
(see `https://chrony-project.org/examples.html#_client_using_public_servers`)
Beacuse of that, the default WARN alert is now set to 1025 seconds.
[//]: # (werk v2)
# Enforce two factor authentication by role or for all users
key | value
---------- | ---
date | 2024-08-08T15:03:40+00:00
version | 2.4.0b1
class | feature
edition | cre
component | wato
level | 1
compatible | yes
Prior to this werk, Two Factor Authentication could not be defined as requirement for Checkmk users. Users with permissions to make changes to _Global Settings_ or _Roles & Permissions_ can now either define all users within the Checkmk site or each user with a specified role must enable Two Factor Authentication.
Enforcing Two Factor based on a user's roles can be enabled via _(Setup > Users > Roles & permissions > Edit role)_.
Enforcing Two Factor for all users can be enabled via _(Setup > General > Global settings > User management > Enforce two factor authentication)_.
Enabling Two Factor for all users will override any role based Two Factor Authentication configurations.
Werk 16120 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# Fixed value of downtimes:is_pending column
key | value
---------- | ---
date | 2024-08-14T12:04:03+00:00
version | 2.4.0b1
class | fix
edition | cre
component | livestatus
level | 1
compatible | yes
The value of the "is_pending" column in the "downtimes" Livestatus table was
inverted, which was a regression since 2.2. This has been fixed.
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
- # Fixed value of dowtimes:is_pending column
+ # Fixed value of downtimes:is_pending column
? +
key | value
---------- | ---
date | 2024-08-14T12:04:03+00:00
version | 2.4.0b1
class | fix
edition | cre
component | livestatus
level | 1
compatible | yes
The value of the "is_pending" column in the "downtimes" Livestatus table was
inverted, which was a regression since 2.2. This has been fixed.
[//]: # (werk v2)
# Add support for SLES 15 SP6
key | value
---------- | ---
date | 2024-08-14T07:25:20+00:00
version | 2.4.0b1
class | feature
edition | cre
component | omd
level | 1
compatible | yes
With this werk, Checkmk is build for SLES 15 SP6
[//]: # (werk v2)
# Use SHA256 digest when baking RPMs
key | value
---------- | ---
date | 2024-08-20T12:18:33+00:00
version | 2.4.0b1
class | feature
edition | cee
component | agents
level | 1
compatible | yes
The agent bakery now uses SHA256 for digests in the package header when creating RPM packages.
Specifically, this means `rpmbuild` is now invoked with the macros
```
%_source_filedigest_algorithm 8
%_binary_filedigest_algorithm 8
```
where `8` signifies SHA256. See `man rpmsign` for further information.
Werk 17240 was deleted. The following Werk is no longer relevant.
[//]: # (werk v2)
# Splunk: improve health service summary
key | value
---------- | ---
date | 2024-08-14T07:54:23+00:00
version | 2.4.0b1
class | feature
edition | cre
component | checks
level | 1
compatible | yes
The previous service summary output:
```console
Overall state: red, File monitor_lnput: red, Index processor: green,
Batchreader-0 - State: green
Buckets - State: green
Tailreader-0 - State: red
```
The new service summary output:
```console
Overall state: red, File monitor input: red (Batchreader-0: green, Tailreader-0: red), Index processor: green (Buckets: green)
```
[//]: # (werk v2)
# check_ewon: TypeError ('NoneType' object is not subscriptable) raised if values for levels are missing
key | value
---------- | ---
compatible | yes
version | 2.4.0b1
date | 2024-08-19T12:13:40+00:00
level | 1
class | fix
component | checks
edition | cre
In case values for `levels` are missing and `None` taken instead, running the check function would
crash with `TypeError ('NoneType' object is not subscriptable)`.
This change hard codes some default values in case no values could be extracted.
[//]: # (werk v2)
# ewon: KeyError (device)
key | value
---------- | ---
date | 2024-08-06T07:48:07+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
An existing rule for `check_ewon` without the mandatory key `device` would result in an exception
`KeyError (device)`.
This change makes the check function use a default, if `device` is not set.
[//]: # (werk v2)
# check_ewon: ValueError (incomplete format)
key | value
---------- | ---
date | 2024-08-06T07:52:50+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
Formatting a value with unit `%` would result in an invalid format-string making `check_ewon`
crash with an exception `ValueError (incomplete format)`.
This change makes `check_ewon` use f-formatting instead of `%`-formatting.