Title: omd cp: Fix etc/ssl/agents/legacy_ca.pem Points to Source of Copy
Class: fix
Compatible: compat
Component: omd
Date: 1707904094
Edition: cre
Level: 1
Version: 2.2.0p23
Since Checkmk 2.2.0 there is a agent CA located in <code>etc/ssl/agents/</code>. This CA is
different from the site CA. In particular, if updating from 2.1.0 to 2.2.0,
Checkmk will create a symlink <code>etc/ssl/agents/legacy_ca.pem</code>, which points to
<code>etc/ssl/ca.pem</code>. After performing an <code>omd cp</code>. This symlink would still point
to the site, which was the source of the copy. The symlink is now relative. If
the site was created with version 2.2.0 or above no symlink is needed.
[//]: # (werk v2)
# aws: Add total reservation utilization service
key | value
---------- | ---
date | 2024-02-14T09:35:02+00:00
version | 2.4.0b1
class | feature
edition | cre
component | checks
level | 1
compatible | yes
This werk adds a service to monitor the total utilization of
reserved resources analogous to the reservation utilization graph
in the AWS cost explorer.
This service is discovered as soon as the AWS agent rule to monitor
costs and usage (CE) is enabled.
[//]: # (werk v2)
# comment: site_id only required when deleting comments by id
key | value
---------- | ---
date | 2024-02-19T17:24:03+00:00
version | 2.4.0b1
class | fix
edition | cre
component | rest-api
level | 1
compatible | no
When deleting a comment via the REST-API, only the 'by_id' option
leaves the comment selection ambiguous, while the options 'params'
or 'query' already have the ability to pinpoint the comment
requested. Therefore, the site_id should is not required in these
cases.
[//]: # (werk v2)
# event_console: site_id only required when deleting ec events by_id
key | value
---------- | ---
date | 2024-02-20T06:46:32+00:00
version | 2.4.0b1
class | fix
edition | cre
component | rest-api
level | 1
compatible | no
When deleting an ec event via the REST-API, only the 'by_id' option
leaves the event selection ambiguous, while the options 'params'
or 'query' already have the ability to pinpoint the event
requested. Therefore, the site_id should is not required in these
cases.
Title: Render service graphs of host independent of historic metrics
Class: fix
Compatible: compat
Component: multisite
Date: 1708328512
Edition: cre
Level: 1
Version: 2.1.0p40
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.
Title: No longer round values for Float and Percentage valuespecs
Class: fix
Compatible: compat
Component: multisite
Date: 1708078850
Edition: cre
Level: 1
Version: 2.2.0p23
The <code>Float</code> and <code>Percentage</code> valuespecs used to round to a specified and limited
number of decimal places.
Now all decimal precision is displayed and used.
Title: Connection test using SNMP credentials configured on host page
Class: fix
Compatible: compat
Component: wato
Date: 1708069326
Edition: cre
Level: 1
Version: 2.2.0p23
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.
Title: Render service graphs of host independent of historic metrics
Class: fix
Compatible: compat
Component: multisite
Date: 1708328512
Edition: cre
Level: 1
Version: 2.2.0p23
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.
Title: iLert notifications: ignore error when event is already closed
Class: fix
Compatible: compat
Component: notifications
Date: 1707321925
Edition: cre
Level: 1
Version: 2.2.0p23
When attempting to resolve an incident which was already manually resolved, an
error occured.
This kind of error will now be ignored.