[//]: # (werk v2)
# Fix assert self._rulespec.item_name is not None
key | value
---------- | ---
date | 2024-02-13T10:08:20+00:00
version | 2.4.0b1
class | fix
edition | cre
component | wato
level | 1
compatible | yes
A `rulespec` may have an `item_spec` without a title. In
[Werk #13387](https://checkmk.com/werk/13387) changed it so that if this title is missing the
the following crash occurs.
```
assert self._rulespec.item_name is not None
```
The occured if one navigates to the parameters via `Parameters for this service` and clicks
`Parameters`. It is now fixed.
[//]: # (werk v2)
# No longer round values for Float and Percentage valuespecs
key | value
---------- | ---
date | 2024-02-16T10:20:50+00:00
version | 2.4.0b1
class | fix
edition | cre
component | multisite
level | 1
compatible | yes
The `Float` and `Percentage` valuespecs used to round to a specified and limited
number of decimal places.
Now all decimal precision is displayed and used.
[//]: # (werk v2)
# Connection test using SNMP credentials configured on host page
key | value
---------- | ---
compatible | yes
version | 2.4.0b1
date | 2024-02-16T07:42:06+00:00
level | 1
class | fix
component | wato
edition | cre
If you used "Save & run connection tests" on the host properties page with SNMP
credentials configured, the configured password was not used for the executed
tests.
A workaround was to enter the password on the "Test connection" page again.
[//]: # (werk v2)
# Render service graphs of host independent of historic metrics
key | value
---------- | ---
date | 2024-02-19T07:41:52+00:00
version | 2.4.0b1
class | fix
edition | cre
component | multisite
level | 1
compatible | yes
The view "Service graphs of host" used to show the error message "No historic metrics recorded but performance data is available. Maybe performance data processing is disabled." even if the underlying single service graphs existed.
This occured especially when using a host check command.
The behavior is fixed to always rendering the service graphs in the view "Service graphs of host", if their performance data is available.
Note that this change does not affect the same error message shown for the "Host graph" row of the "Status of Host" view, as the available performance data belongs to the services and not to the host.
[//]: # (werk v2)
# iLert notifications: ignore error when event is already closed
key | value
---------- | ---
date | 2024-02-07T16:05:25+00:00
version | 2.4.0b1
class | fix
edition | cre
component | notifications
level | 1
compatible | yes
When attempting to resolve an incident which was already manually resolved, an
error occured.
This kind of error will now be ignored.
[//]: # (werk v2)
# Dedicated security logging
key | value
---------- | ---
date | 2024-02-16T09:38:25+00:00
version | 2.4.0b1
class | feature
edition | cre
component | omd
level | 1
compatible | yes
To make it easier to detect certain security relevant events a dedicated security log is introduced. You can find it in `var/log/security.log`.
The format of each line is:
1. The date and time the logentry was created (local time)
2. The security domain and the process id.
3. The message as json with a `summary` and `details` key. The contents of the `details` vary by the domain.
Currently the following domains exist:
* `application_errors`: e.g if a CSRF token could not be found/validated
* `auth`: e.g. successful / unsuccessful authentication attempts. (Successful authentication attempts without opening a session are currently not logged.)
* `service`: e.g. the start of a site
* `user_management`: e.g. change of a password
Please note that this logfile is still subject to change. Additional events might be added and details may change with p-releases.
Werk 16491 was deleted. The following Werk is no longer relevant.
[//]: # (werk v2)
# netapp_ontap_snapvault: fix levels param rule configuration
key | value
---------- | ---
date | 2024-02-13T10:06:38+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
This problem impacted the configuration of the levels of the lag time monitoring of snapvault services: configuring levels caused a crash.
Title: cmk-update-config: Don't Read Characters Pressed before Prompt Appears
Class: fix
Compatible: compat
Component: omd
Date: 1707920976
Edition: cre
Level: 1
Version: 2.2.0p23
During <code>cmk-update-config</code> can prompt you with questions about how to continue the update. This
is an example.
C+:
Exception while trying to load rulesets:
You can abort the update process (A) and try to fix the incompatibilities or try to continue the update (c).
Abort update? [A/c]
C-:
Previously, these prompts would read input, which was typed before the prompt was shown. Now, only
the input is read after the prompt is shown.
[//]: # (werk v2)
# cmk-update-config: Don't Read Characters Pressed before Prompt Appears
key | value
---------- | ---
date | 2024-02-14T14:29:36+00:00
version | 2.4.0b1
class | fix
edition | cre
component | omd
level | 1
compatible | yes
During `cmk-update-config` can prompt you with questions about how to continue the update. This
is an example.
```
Exception while trying to load rulesets:
You can abort the update process (A) and try to fix the incompatibilities or try to continue the update (c).
Abort update? [A/c]
```
Previously, these prompts would read input, which was typed before the prompt was shown. Now, only
the input is read after the prompt is shown.