[//]: # (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.
Title: service_discovery: Fixed internal server error on service discovery when IP cannot be resolved
Class: fix
Compatible: compat
Component: rest-api
Date: 1707741261
Edition: cre
Level: 1
Version: 2.2.0p23
Prior to this Werk, when a service discovery was requested from a host whose IP could not be resolved, the endpoint returned a 500 error status (Internal Server Error). This Werk corrects this behavior and now returns error code 400.
Title: Show full agent hash in Check_MK Agent service and Agent update status
Class: fix
Compatible: compat
Component: agents
Date: 1707986354
Edition: cee
Level: 1
Version: 2.2.0p23
As an addition to Werk #15424, the <em>Check_MK Agent</em> service and the
<em>Agent update status</em> page now also show the full 16-digit agent hash.
[//]: # (werk v2)
# Bi: creating rules should allow the same host/service label group format as the response
key | value
---------- | ---
date | 2024-02-16T13:37:01+00:00
version | 2.4.0b1
class | fix
edition | cre
component | rest-api
level | 1
compatible | yes
This werk makes it possible to create a BI rule via the REST-API using the same schema
that is returned in a response. Previously, this was not possible after some changes
to how our label_groups are now configured.
[//]: # (werk v2)
# Show full agent hash in Check_MK Agent service and Agent update status
key | value
---------- | ---
date | 2024-02-15T08:39:14+00:00
version | 2.4.0b1
class | fix
edition | cee
component | agents
level | 1
compatible | yes
As an addition to Werk #15424, the *Check_MK Agent* service and the
*Agent update status* page now also show the full 16-digit agent hash.