[//]: # (werk v2)
# azure: Remove unnecessary 'metric not found' errors
key | value
---------- | ---
compatible | yes
version | 2.4.0b1
date | 2024-08-08T15:40:36+00:00
level | 1
class | fix
component | checks
edition | cre
When querying metrics, Azure agent was reporting each missing metric in the
details of the 'Azure Agent Info' service. This didn't influence the status
of the service but still implied an error.
It was misleading because some metrics aren't defined in some types
of resources. Now, those metrics are optional and won't cause an error.
[//]: # (werk v2)
# Microsoft Teams: Updated notification message
key | value
---------- | ---
date | 2024-08-15T09:01:50+00:00
version | 2.4.0b1
class | fix
edition | cre
component | notifications
level | 1
compatible | yes
Changes were made to the notification format for Microsoft Teams to reduce
whitespace. No user action is required.
Formatting rules for the details:
* Supports Markdown, see [Microsoft's documentation](https://learn.microsoft.com/en-us/adaptive-cards/authoring-c…
* Use `\n\n` for a new line
* An empty line will lead to a separator (`\n\n\n\n`)
[//]: # (werk v2)
# Fixed CMC crash when sending illegal metrics to InfluxDB
key | value
---------- | ---
date | 2024-08-14T14:17:10+00:00
version | 2.4.0b1
class | fix
edition | cee
component | cmc
level | 1
compatible | yes
When the CMC tried to send to a metric to an InfluxDB where the metric name
was malformed (e.g. starting with an underscore), the CMC crashed. This
has been fixed, such metrics are now simply forwarded to the InfluxDB. The
latter will probably be a bit unhappy about such metric names, but this can
be figured out via its logs, and the corresponding check can be fixed.
Note that in a future Checkmk version, we will probably drop such metrics
silently, logging this only for higher log levels to avoid log spam at the
default log settings.
[//]: # (werk v2)
# mysql_slave: propagate errors to service result
key | value
---------- | ---
date | 2024-08-13T12:05:09+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | no
You may be affected by this change if you monitor MySQL servers and you do not
have an `mysql_slave` service to monitor the "Slave Sync Status".
`mysql_slave` ignored the result and did not discover a service if the section
contained an error.
Now, in case the item section consists of a single line that looks like a MySQL
error message, the error message is propagated to the check result with an
`CRIT` status.
If you rediscover services on your MySQL hosts and see a critical `mysql_slave`
service, then this service probably always returned this error, but is was not
shown in your monitoring system in the past.
Please consult the error message and decide if you want to fix the Problem
described in the error message. If you don't want to monitor you the "Slave Sync
Status" of your MySQL database you may also disable the service discovery for
this item.
[//]: # (werk v2)
# Fixed value of dowtimes:is_pending column
key | value
---------- | ---
date | 2024-08-14T12:04:03+00:00
version | 2.4.0b1
class | fix
edition | cre
component | livestatus
level | 1
compatible | yes
The value of the "is_pending" column in the "downtimes" Livestatus table was
inverted, which was a regression since 2.2. This has been fixed.
[//]: # (werk v2)
# Splunk: improve health service summary
key | value
---------- | ---
date | 2024-08-14T07:54:23+00:00
version | 2.4.0b1
class | feature
edition | cre
component | checks
level | 1
compatible | yes
The previous service summary output:
```console
Overall state: red, File monitor_lnput: red, Index processor: green,
Batchreader-0 - State: green
Buckets - State: green
Tailreader-0 - State: red
```
The new service summary output:
```console
Overall state: red, File monitor input: red (Batchreader-0: green, Tailreader-0: red), Index processor: green (Buckets: green)
```
[//]: # (werk v2)
# Fix error on publishing forcast or custom graphs to sites
key | value
---------- | ---
date | 2024-08-12T09:05:41+00:00
version | 2.4.0b1
class | fix
edition | cee
component | multisite
level | 1
compatible | yes
If you used the option "Publish to users of sites" an error like "TypeError:
('sites', ['MYSITE'])" occured.
A workaround was to move the custom graph file of the user within
~/var/check_mk/web/USERNAME.
Note: This will result in a loss of the users custom graphs.
[//]: # (werk v2)
# Add missing "Remove downtime" button
key | value
---------- | ---
date | 2024-08-13T12:27:28+00:00
version | 2.4.0b1
class | fix
edition | cre
component | multisite
level | 1
compatible | yes
The button was missing on the views "Downtimes of host" and "Downtimes of
service" but still available via the "Commands" menu.
[//]: # (werk v2)
# Fix "Discovery state" filter
key | value
---------- | ---
date | 2024-08-13T14:11:48+00:00
version | 2.4.0b1
class | fix
edition | cre
component | multisite
level | 1
compatible | yes
The filter "Discovery state" used, e.g. in the "Unmonitored services" view, was
non-functional since version 2.3. No results were shown.