Title: Build Checkmk for Ubuntu-23.10 (mantic minotaur)
Class: feature
Compatible: compat
Component: omd
Date: 1699612013
Edition: cre
Knowledge: undoc
Level: 1
State: unknown
Version: 2.1.0p37
With this werk, we deliver builds for Ubuntu-23.10.
<b>PLEASE NOTE:</b>
This will be the last STS Ubuntu version we will provide to the public.
Have a look at https://docs.checkmk.com/latest/en/update_matrix.html#ossupport
Title: logwatch_ec: Duplicate messages forwarded to event console
Class: fix
Compatible: compat
Component: checks
Date: 1701810299
Edition: cre
Level: 1
Version: 2.1.0p38
This fixes duplicate messages forwarded to the event console by the plugin <i>"Forward Logwatch Messages to the Event Console"</i> (<tt>logwatch_ec</tt>).
It only affects users that configured it to monitore multiple logfiles in one common service.
Users who need an instant solution and cannot wait for the next patch release can change their settings to mitigate the issue.
By checking <i>"Create a separate check for each logfile"</i> in the relevant <i>"Logwatch Event Console Forwarding"</i> rule and rediscovering the host you can switch to a configuration that is not affected.
Title: rabbitmq_cluster_messages: Most of the configrable parametes have not been considered
Class: fix
Compatible: compat
Component: checks
Date: 1701894663
Edition: cre
Level: 1
Version: 2.1.0p38
Most of the parameters configurable in the ruleset <i>"RabbitMQ cluster messages"</i> have not been considered by the plugin.
Title: discovery: better message in case of failing data sources
Class: fix
Compatible: compat
Component: checks
Date: 1701963693
Edition: cre
Level: 1
Version: 2.2.0p17
With the werk 15242, bulk discovery and periodic service discovery report errors
if fetching from one of the data sources failed. Additionally, autodiscovery won't make
changes to the configuration in that case.
The discovery service still showed a message 'rediscovery scheduled' which was confusing
to the users. Now, the message 'Automatic rediscovery currently not possible due to failing
data source(s). Please run service discovery manually' will be shown in case of failing data
sources.
Title: logwatch_ec: Duplicate messages forwarded to event console
Class: fix
Compatible: compat
Component: checks
Date: 1701810299
Edition: cre
Level: 1
Version: 2.2.0p17
This fixes duplicate messages forwarded to the event console by the plugin <i>"Forward Logwatch Messages to the Event Console"</i> (<tt>logwatch_ec</tt>).
It only affects users that configured it to monitore multiple logfiles in one common service.
Users who need an instant solution and cannot wait for the next patch release can change their settings to mitigate the issue.
By checking <i>"Create a separate check for each logfile"</i> in the relevant <i>"Logwatch Event Console Forwarding"</i> rule and rediscovering the host you can switch to a configuration that is not affected.
Title: rabbitmq_cluster_messages: Most of the configrable parametes have not been considered
Class: fix
Compatible: compat
Component: checks
Date: 1701894663
Edition: cre
Level: 1
Version: 2.2.0p17
Most of the parameters configurable in the ruleset <i>"RabbitMQ cluster messages"</i> have not been considered by the plugin.
Title: discovery: better message in case of failing data sources
Class: fix
Compatible: compat
Component: checks
Date: 1701963693
Edition: cre
Level: 1
Version: 2.3.0b1
With the werk 15242, bulk discovery and periodic service discovery report errors
if fetching from one of the data sources failed. Additionally, autodiscovery won't make
changes to the configuration in that case.
The discovery service still showed a message 'rediscovery scheduled' which was confusing
to the users. Now, the message 'Automatic rediscovery currently not possible due to failing
data source(s). Please run service discovery manually' will be shown in case of failing data
sources.
Title: logwatch_ec: Duplicate messages forwarded to event console
Class: fix
Compatible: compat
Component: checks
Date: 1701810299
Edition: cre
Level: 1
Version: 2.3.0b1
This fixes duplicate messages forwarded to the event console by the plugin <i>"Forward Logwatch Messages to the Event Console"</i> (<tt>logwatch_ec</tt>).
It only affects users that configured it to monitore multiple logfiles in one common service.
Users who need an instant solution and cannot wait for the next patch release can change their settings to mitigate the issue.
By checking <i>"Create a separate check for each logfile"</i> in the relevant <i>"Logwatch Event Console Forwarding"</i> rule and rediscovering the host you can switch to a configuration that is not affected.
Title: rabbitmq_cluster_messages: Most of the configrable parametes have not been considered
Class: fix
Compatible: compat
Component: checks
Date: 1701894663
Edition: cre
Level: 1
Version: 2.3.0b1
Most of the parameters configurable in the ruleset <i>"RabbitMQ cluster messages"</i> have not been considered by the plugin.