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.
Title: "Aggregation of Downtimes" BI option had no effect
Class: fix
Compatible: compat
Component: bi
Date: 1707983290
Edition: cre
Level: 1
Version: 2.2.0p23
The option should change the computation of downtimes from CRIT to WARN but did
not. This has been fixed.
Title: nfsiostat: resolve error when displaying graphs
Class: feature
Compatible: compat
Component: checks
Date: 1707734651
Edition: cre
Level: 1
Version: 2.2.0p23
There was an error in the nfsiostat plugin where it tried
to report some data in units not supported by the graphing
system which made viewing its service graphs impossible.
This werk changes the units that were reported to our
visualizations and now the graphs render all data appropriately.
Title: Fix notifications postponed forever with Use the status of the service
Class: fix
Compatible: compat
Component: notifications
Date: 1707925534
Edition: cee
Level: 1
Version: 2.2.0p23
Configuring a service with "host check command > use the status of the service"
would result in notifications for any service to be postponed forever. This has
been fixed.
[//]: # (werk v2)
# service_discovery: Fixed internal server error on service discovery when IP cannot be resolved
key | value
---------- | ---
date | 2024-02-12T12:34:21+00:00
version | 2.4.0b1
class | fix
edition | cre
component | rest-api
level | 1
compatible | yes
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.