[//]: # (werk v2)
# Microsoft Teams: Updated notification message
key | value
---------- | ---
date | 2024-08-15T09:01:50+00:00
version | 2.3.0p13
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)
# mk-sql can monitor bound to IP Sql Server instances
key | value
---------- | ---
date | 2024-08-14T16:02:54+00:00
version | 2.3.0p13
class | feature
edition | cee
component | checks
level | 1
compatible | yes
The mk-sql plugin was previously unable to monitor
instances that were bound to a specific IP address
(the "Listen All" option was turned off).
This issue has been resolved in the latest release.
The mk-sql plugin can now successfully monitor such
instances.
[//]: # (werk v2)
# Fixed CMC crash when sending illegal metrics to InfluxDB
key | value
---------- | ---
date | 2024-08-14T14:17:10+00:00
version | 2.3.0p13
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)
# Fixed value of dowtimes:is_pending column
key | value
---------- | ---
date | 2024-08-14T12:04:03+00:00
version | 2.3.0p13
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)
# Fix error on publishing forcast or custom graphs to sites
key | value
---------- | ---
date | 2024-08-12T09:05:41+00:00
version | 2.3.0p13
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)
# Save scrollbar position on page load
key | value
---------- | ---
compatible | yes
version | 2.3.0p13
date | 2024-08-12T11:33:16+00:00
level | 1
class | fix
component | multisite
edition | cre
The sidebar of the main frame always scrolled up to the top after the page
load.
This was an issue if you e.g. edited large views and already scrolled down
before the whole page was loaded.
[//]: # (werk v2)
# Add missing "Remove downtime" button
key | value
---------- | ---
date | 2024-08-13T12:27:28+00:00
version | 2.3.0p13
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.3.0p13
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.
[//]: # (werk v2)
# Better handling of notification result in case of timeout
key | value
---------- | ---
compatible | yes
version | 2.3.0p13
date | 2024-06-05T09:42:42+00:00
level | 1
class | fix
component | notifications
edition | cre
Werk #16707 added useful log information to failed notifications in case of a timeout.
In some cases, this log contained also script output.
We now show the timeout message within "Summary" of the notification result
and, if available, the last output of the notification plugin followed by the
timeout message within the "Comment" column. Both are separated by "--".