Title: logwatch_ec: remove spool files after reading them
Class: fix
Compatible: compat
Component: checks
Date: 1698764921
Edition: cre
Level: 1
Version: 2.2.0p15
Before this fix spool files were only removed when they were too old or if
there were too many of them.
Spool files that got deleted after reading will be recreated if there was
an error while sending a message.
Title: mssql_backup: Correct timezone difference for last backup date
Class: fix
Compatible: compat
Component: checks
Date: 1696949130
Edition: cre
Knowledge: doc
Level: 1
Version: 2.3.0b1
This werk is relevant for users monitoring the age of the last backup time of mssql databases in different timezones.
The date/time of the last backup of a mssql database is currently stored in local host time without the information about the host timezone. When this time is used to check the age of the last backup, it is interpreted in the Checkmk server timezone.
When using different timezones, this leads to incorrect values for "Age of last database backup" and if the age is negative, in newer Checkmk versions to the warning "Cannot reasonably calculate time since last backup (hosts time running ahead)".
The mssql agent plugin will now store the time in UTC and the mssql_backup check will interpret the time accordingly.
You will need to update the agent plugin mssql.vbs to receive the corrected times.
Werk 16259 was deleted. The following Werk is no longer relevant.
Title: Changed local override mechanism for Checkmk plugins
Class: feature
Compatible: incomp
Component: checks
Date: 1700031909
Edition: cre
Level: 1
Version: 2.3.0b1
This Werk affects users that have modified existing plugins shipped with Checkmk (or intend to do so in the future).
Other plugins are not affected by this change.
In Checkmk, users can "hide" shipped plugin files by putting a corresponding file with the same path in the sites <tt>local/</tt> folder.
Checkmk will always prefer the files found there over the shipped ones, allowing users to effectively "patch" a sites plugins.
While this mechanism <i>probably</i> will continue to work (<i>maybe</i>), it is discouraged and no longer supported.
Users that want to modify, replace or extend an existing plugin are advised to make a copy of the plugin, <b>give it a new name</b> and disable the shipped one in the <i>Setup</i>.
We believe this step is necessary in order to provide a good user experience for plugin developers and a smooth upgrade process for plugin users.
These are the main reasons:
<ul>
<li>
While the APIs for plugin development deliberately do not care about the files names the plugins are in, the current mechanism works based on a file name.
This effectively makes the file name part of the APIs.
Strictly speaking, moving a plugin to a different file (or splitting large files up) would require an incompatible Werk, as it might break users local overrides.
This was mostly not done in the past, and is not sustainable in the future.
(Also the Werk only alerts users to the problem, they would still have to deal with it).
</li>
<li>
In the wake of new APIs for plugin development (corresponding Werks will follow), plugins will be moved to new locations in the filesystem a lot, exacerbating the above problem.
</li>
<li>
One of the advantages of the future APIs will be that plugins are bundled by their topic (e.g. all plugins related to Kubernetes might be found in <tt>cmk/plugins/kube</tt>, be it special agents, <i>WATO</i> rulespecs, check plugins or graph definitions).
As a result, some changes to the plugin loading mechanism have to be made, resulting in hard to predict results if combined with the above shadowing mechanism.
</li>
</ul>
Title: Avoid duplicate port allocations within the same site
Class: fix
Compatible: compat
Component: omd
Date: 1700140615
Edition: cre
Knowledge: undoc
Level: 1
State: unknown
Version: 2.1.0p37
When configuring ports via <tt>omd config</tt>, Checkmk checks if the configured port is already in
use, both by the same site and by other sites. The check if the port is already in use by another
process of the same site was broken, which could lead to duplicate port allocations within a site.
Title: Build Checkmk for Ubuntu-23.10 (mantic minotaur)
Class: feature
Compatible: compat
Component: omd
Date: 1699612013
Edition: cre
Knowledge: undoc
Level: 1
Version: 2.2.0p15
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: Fix color of Perf-O-Meter for CPU utilization
Class: fix
Compatible: compat
Component: wato
Date: 1700145079
Edition: cre
Knowledge: undoc
Level: 1
State: unknown
Version: 2.2.0p15
The color for the Perf-O-Meter of the CPU utilization lead to hardly readable text in the light theme of Checkmk. This is now fixed.
Title: ical imports: valid iCalendar files not being accepted on import
Class: fix
Compatible: compat
Component: wato
Date: 1700150397
Edition: cre
Knowledge: undoc
Level: 1
State: unknown
Version: 2.2.0p15
iCalendar files with new lines at the end file were failing to import.
This werk addresses the issue by allowing iCalendar files that endwith
a newline character or not.
Title: Avoid duplicate port allocations within the same site
Class: fix
Compatible: compat
Component: omd
Date: 1700140615
Edition: cre
Knowledge: undoc
Level: 1
State: unknown
Version: 2.2.0p15
When configuring ports via <tt>omd config</tt>, Checkmk checks if the configured port is already in
use, both by the same site and by other sites. The check if the port is already in use by another
process of the same site was broken, which could lead to duplicate port allocations within a site.