Werk 16210 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# folder_config: Prevent unintentional deletion of a non-empty folder
key | value
---------- | ---
date | 2024-01-11T09:34:55+00:00
version | 2.4.0b1
class | fix
edition | cre
component | rest-api
level | 1
compatible | no
Prior to this Werk, the REST API could delete non-empty folders without any further check. With this Werk, the endpoint now accepts the **delete_method** query parameter. The possible values are:
- **recursive**: Deletes the folder and all the elements it contains.
- **abort_on_nonempty**: Deletes the folder only if it is not empty
If no delete_method is provided, **recursive** is asumed and the behaviour is the same as before this Werk.
The enpoint will return a 409 status code when trying to delete a folder that contains hosts, rules, subfolders or is referenced by another object.
Use example:
`curl -X 'DELETE' 'http://example.com/my_site/check_mk/api/1.0/objects/folder_config/my_folder…' -H 'accept: */*`
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
# folder_config: Prevent unintentional deletion of a non-empty folder
key | value
---------- | ---
date | 2024-01-11T09:34:55+00:00
- version | 2.3.0b1
? ^
+ version | 2.4.0b1
? ^
class | fix
edition | cre
component | rest-api
level | 1
compatible | no
Prior to this Werk, the REST API could delete non-empty folders without any further check. With this Werk, the endpoint now accepts the **delete_method** query parameter. The possible values are:
- **recursive**: Deletes the folder and all the elements it contains.
- **abort_on_nonempty**: Deletes the folder only if it is not empty
If no delete_method is provided, **recursive** is asumed and the behaviour is the same as before this Werk.
The enpoint will return a 409 status code when trying to delete a folder that contains hosts, rules, subfolders or is referenced by another object.
Use example:
`curl -X 'DELETE' 'http://example.com/my_site/check_mk/api/1.0/objects/folder_config/my_folder…' -H 'accept: */*`
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.4.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.
Title: Extend devices found by apc_ats_status
Class: fix
Compatible: compat
Component: checks
Date: 1709123851
Edition: cre
Level: 1
Version: 2.1.0p41
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.
Title: Extend devices found by apc_ats_status
Class: fix
Compatible: compat
Component: checks
Date: 1709123851
Edition: cre
Level: 1
Version: 2.2.0p24
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.
Title: Path to mysql.ini under Windows for mk_sql
Class: fix
Compatible: compat
Component: checks
Date: 1708687568
Edition: cre
Level: 1
Version: 2.2.0p24
If you've been using mysql and the corresponding agent plugin <em>mk_sql</em>
under Windows, the plugin may have crashed and the agent output would then
show the following error:
C+:
<<<mysql_ping>>>
[[MySQL83]]
mysqladmin: File '\etc\check_mk\mysql.local.ini' not found (OS errno 2 - No such file or directory)
mysqladmin: [ERROR] Stopped processing the 'include' directive in file C:\ProgramData\checkmk\agent\config\mysql.ini at line 8.
C-:
Under Windows, the plugin config path <code>C:\ProgramData\checkmk\agent\config</code> is now used.
In contrast to the corresponding Linux plugin <code>mk_mysql</code>, the config path under Windows cannot be changed.
Title: check_mailboxes: fix check of multiple mailboxes
Class: fix
Compatible: compat
Component: checks
Date: 1709557446
Edition: cre
Level: 1
Version: 2.2.0p24
When selecting to check multiple mailboxes, the software always checked only the last specified mailbox.
This werk fixes this behaviour.
[//]: # (werk v2)
# netapp_ontap_temp: restore check of list of sensors
key | value
---------- | ---
date | 2024-02-26T17:16:55+00:00
version | 2.4.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.
+