[//]: # (werk v2)
# omd: trigger openapi-spec generation job during start, restart and reload
key | value
---------- | ---
date | 2024-02-29T13:06:16+00:00
version | 2.3.0b2
class | feature
edition | cre
component | omd
level | 1
compatible | yes
Werk 15724 introduces a mechanism for regenerating the API specification,
which, in certain instances, is executed as a background job due to the
potential time required for completion. This update modifies the omd start,
restart, and reload commands to initiate this specific background job upon
execution. Users should be aware that triggering the job does not result
in immediate availability of the updated documentation; there may be a
delay before the documentation is updated. This saves the user from having
to trigger and wait for the specification regeneration manually in case
relevant changes have been made outside the user interface and the apache
process needs to be restarted.
Based on werk 15724 the specification is now updated in these situations:
* post-create hook: Create the initial spec after a site has been created
* post rename action: Update the spec after a site has been copied, restored or renamed
* update-config action: Update the spec after the site has been updated
* omd apache: Update the spec when the apache process is started, restarted or reloaded
Werk 16239 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# Extend devices found by apc_ats_status
key | value
---------- | ---
compatible | yes
version | 2.3.0b2
date | 2024-02-28T12:37:31+00:00
level | 1
class | fix
component | checks
edition | cre
This werk affects you, in case you try to monitor your APC Rack Automatic Transfer Switch with <tt>apc_ats_status</tt>.
Previously some devices were not discovered due to a too strict scan function.
Futher, we enable monitoring other power supplies available at such devices as for example 1V and 3.3V.
This was fixed now.
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
# Extend devices found by apc_ats_status
key | value
---------- | ---
compatible | yes
- version | 2.3.0b1
? ^
+ version | 2.3.0b2
? ^
date | 2024-02-28T12:37:31+00:00
level | 1
class | fix
component | checks
edition | cre
This werk affects you, in case you try to monitor your APC Rack Automatic Transfer Switch with <tt>apc_ats_status</tt>.
Previously some devices were not discovered due to a too strict scan function.
Futher, we enable monitoring other power supplies available at such devices as for example 1V and 3.3V.
This was fixed now.
+
Werk 16310 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# Rework of "Automatically update service configuration" option
key | value
---------- | ---
date | 2024-01-19T12:59:21+00:00
version | 2.3.0b1
class | feature
edition | cre
component | wato
level | 1
compatible | yes
This option is used in the service discovery rule "Periodic service discovery"
and the global option "Bulk discovery" and offers now the possibility to choose
between a refresh of all services and host labels or a custom configuration. If
you choose a custom one, you can select "Monitor undecided services", "Remove
vanished services" and/or "Update host labels".
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
# Rework of "Automatically update service configuration" option
key | value
---------- | ---
date | 2024-01-19T12:59:21+00:00
version | 2.3.0b1
class | feature
edition | cre
component | wato
level | 1
compatible | yes
+ This option is used in the service discovery rule "Periodic service discovery"
+ and the global option "Bulk discovery" and offers now the possibility to choose
+ between a refresh of all services and host labels or a custom configuration. If
+ you choose a custom one, you can select "Monitor undecided services", "Remove
+ vanished services" and/or "Update host labels".
-
[//]: # (werk v2)
# Extend devices found by apc_ats_status
key | value
---------- | ---
compatible | yes
version | 2.3.0b1
date | 2024-02-28T12:37:31+00:00
level | 1
class | fix
component | checks
edition | cre
This werk affects you, in case you try to monitor your APC Rack Automatic Transfer Switch with <tt>apc_ats_status</tt>.
Previously some devices were not discovered due to a too strict scan function.
Futher, we enable monitoring other power supplies available at such devices as for example 1V and 3.3V.
This was fixed now.
[//]: # (werk v2)
# netapp_ontap_temp: restore check of list of sensors
key | value
---------- | ---
date | 2024-02-26T17:16:55+00:00
version | 2.3.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
The above-mentioned plugin now monitors the list of ambient and internal temperature sensors,
sticking to the logic of the netapp_api_temp plugin (old Netapp API).
A re-discovery is needed to monitor the new services.
Werk 15292 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: Changelog will only contain Werks from current major version
Class: fix
Compatible: compat
Component: wato
Date: 1693224813
Edition: cre
Knowledge: doc
Level: 1
Version: 2.3.0b1
Checkmk has a built in changelog viewer that shows Changelog items called
"Werks". For previous versions of checkmk it showed "Werks" for all versions of
Checkmk.
It turned out that the changelog was not complete: For previous major versions
of Checkmk not all Werks were displayed. As there is little benefit to display
Werks of previous major versions of checkmk we decided to remove those.
The whole list of all Werks is available on our homepage:
https://checkmk.com/werks
When updating to a new major version, the update process will check if there
are unacknowledged werks and tell the user about this, as this list will no
longer be available after the update.
This check is omitted for remote sites in a distributed configuration
environment, as long as both the remote site and the central site are running
at least version 2.3.0 of Checkmk.
------------------------------------<diff>-------------------------------------------
Title: Changelog will only contain Werks from current major version
Class: fix
Compatible: compat
Component: wato
Date: 1693224813
Edition: cre
Knowledge: doc
Level: 1
Version: 2.3.0b1
Checkmk has a built in changelog viewer that shows Changelog items called
"Werks". For previous versions of checkmk it showed "Werks" for all versions of
Checkmk.
It turned out that the changelog was not complete: For previous major versions
of Checkmk not all Werks were displayed. As there is little benefit to display
Werks of previous major versions of checkmk we decided to remove those.
The whole list of all Werks is available on our homepage:
https://checkmk.com/werks
When updating to a new major version, the update process will check if there
are unacknowledged werks and tell the user about this, as this list will no
longer be available after the update.
+ This check is omitted for remote sites in a distributed configuration
+ environment, as long as both the remote site and the central site are running
+ at least version 2.3.0 of Checkmk.
+
[//]: # (werk v2)
# check_mailboxes: fix check of multiple mailboxes
key | value
---------- | ---
date | 2024-03-04T13:04:06+00:00
version | 2.3.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
When selecting to check multiple mailboxes, the software always checked only the last specified mailbox.
This werk fixes this behaviour.
[//]: # (werk v2)
# mssql_backup: Correct timezone difference for last backup date
key | value
---------- | ---
compatible | yes
version | 2.3.0b1
date | 2023-10-10T14:45:30+00:00
level | 1
class | fix
component | checks
edition | cre
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 15839 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# Connection state of interface on Windows is supported out-of-the-box
key | value
---------- | ---
date | 2024-02-22T08:27:57+00:00
version | 2.3.0b1
class | feature
edition | cre
component | checks
level | 2
compatible | yes
Previously, users were required to install an additional plugin to
determine the state of a network interface on Windows.
With the current release, this functionality is now integrated directly into the
Windows agent, eliminating the need for extra plugins.
For enhanced consistency across operating systems, network interfaces that are
operational are now marked as `up`, and those that are not available are marked
as `down`, aligning with the terminology used on Linux.
This change may lead to critical alerts with interfaces correctly reported as
`down`, which have been in that state for a long time but were previously
erroneously reported as `Connected`.
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
# Connection state of interface on Windows is supported out-of-the-box
key | value
---------- | ---
date | 2024-02-22T08:27:57+00:00
version | 2.3.0b1
class | feature
edition | cre
component | checks
level | 2
compatible | yes
Previously, users were required to install an additional plugin to
determine the state of a network interface on Windows.
With the current release, this functionality is now integrated directly into the
Windows agent, eliminating the need for extra plugins.
For enhanced consistency across operating systems, network interfaces that are
operational are now marked as `up`, and those that are not available are marked
as `down`, aligning with the terminology used on Linux.
+ This change may lead to critical alerts with interfaces correctly reported as
+ `down`, which have been in that state for a long time but were previously
+ erroneously reported as `Connected`.
+
+
[//]: # (werk v2)
# Agent updates failing on Solaris 10
key | value
---------- | ---
date | 2024-03-01T08:43:58+00:00
version | 2.3.0b1
class | fix
edition | cee
component | agents
level | 1
compatible | no
On some Solaris 10 systems, an agent update did crash with error message
```
/var/sadm/pkg/check-mk-agent/install/postremove: syntax error at line 19: `(' unexpected
pkgrm: ERROR: postremove script did not complete successfully
```
If you ran into this error, to make the update perform again, please delete the file
`/var/sadm/pkg/check-mk-agent/install/postremove` on affected systems.
Technical background:\
The postremove script used the subshell evaluation syntax `$(...)` that is incompatible to the standard `bin/sh` shell found on some Solaris 10 systems.