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.
[//]: # (werk v2)
# Respect timerange for all view elements in report
key | value
---------- | ---
compatible | yes
version | 2.4.0b1
date | 2024-02-09T10:20:05+00:00
level | 1
class | fix
component | reporting
edition | cee
If a report with more than one view element was created e.g. via the report
snapin, the defined timerange was only set from the second view element on.
[//]: # (werk v2)
# notification_rule: allow custom plugin names when selecting cancel without a restart
key | value
---------- | ---
date | 2024-02-14T13:46:22+00:00
version | 2.4.0b1
class | fix
edition | cre
component | rest-api
level | 1
compatible | yes
We recently made a change that would allow you to create a notification rule,
via the REST-API using a custom plugin but also setting the option
"cancel_previous_notifications". However, an apache restart was required
since we were verifying the custom plugin via the runtime generated
schema. This werk fixes this issue by removing this verification from the
schema and checking at the endpoint.
[//]: # (werk v2)
# "Aggregation of Downtimes" BI option had no effect
key | value
---------- | ---
compatible | yes
version | 2.4.0b1
date | 2024-02-15T07:48:10+00:00
level | 1
class | fix
component | bi
edition | cre
The option should change the computation of downtimes from CRIT to WARN but did
not. This has been fixed.
Werk 15584 was deleted. The following Werk is no longer relevant.
Title: mk_docker: Added podman support
Class: feature
Compatible: compat
Component: checks
Date: 1683627763
Edition: cre
Knowledge: undoc
Level: 1
Version: 2.3.0b1
Added podman support in mk_docker.py.
This way the plugin ends in case it is being executed on a non docker or podman host.
[//]: # (werk v2)
# Fix notifications postponed forever with Use the status of the service
key | value
---------- | ---
date | 2024-02-14T15:45:34+00:00
version | 2.4.0b1
class | fix
edition | cee
component | notifications
level | 1
compatible | yes
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.
Title: EC: Fix missing update action for CRE
Class: fix
Compatible: compat
Component: ec
Date: 1707986872
Edition: cre
Level: 1
Version: 2.2.0p23
With werk 16012 the active configuration folder was introduced. During an
update the event console configuration is synchronized to this folder which is
missing for the raw edition. Fixed that.