Checkmk werks level1

checkmk-werks-lvl1@lists.checkmk.com

1 participants
15927 discussions

[2.4.0] Checkmk Werk 16501 created: omd: trigger openapi-spec generation job during start, restart and reload

by Checkmk werks level 1

[//]: # (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.4.0b1 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

6 months, 3 weeks

[2.4.0] Checkmk Werk 16579 created: downtimes: Added 'modify downtimes' endpoint

by Checkmk werks level 1

[//]: # (werk v2) # downtimes: Added 'modify downtimes' endpoint key | value ---------- | --- date | 2024-03-01T10:46:38+00:00 version | 2.4.0b1 class | feature edition | cre component | rest-api level | 1 compatible | yes With this Werk a new endpoint for modifying downtimes is incorporated. It is possible to modify the comment and the end timestamp as in the GUI. The selection of downtimes to modify can be done by id, by query, or by hostname and service description. Method: PUT URL: domain-types/downtime/actions/modify/invoke

6 months, 3 weeks

[2.4.0] Checkmk Werk 16210 adapted: folder_config: Prevent unintentional deletion of a non-empty folder

by Checkmk werks level 1

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: */*`

6 months, 3 weeks

[2.1.0] Checkmk Werk 16502 created: dcd: resolve log error in case of discovery timeouts

by Checkmk werks level 1

Title: dcd: resolve log error in case of discovery timeouts Class: fix Compatible: compat Component: dcd Date: 1709716462 Edition: cee Level: 1 Version: 2.1.0p41

6 months, 3 weeks

[2.3.0] Checkmk Werk 16310 adapted: Rework of "Automatically update service configuration" option

by Checkmk werks level 1

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". -

6 months, 3 weeks

[2.4.0] Checkmk Werk 16239 created: Extend devices found by apc_ats_status

by Checkmk werks level 1

[//]: # (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.

6 months, 3 weeks

[2.1.0] Checkmk Werk 16239 created: Extend devices found by apc_ats_status

by Checkmk werks level 1

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.

6 months, 3 weeks

[2.2.0] Checkmk Werk 16239 created: Extend devices found by apc_ats_status

by Checkmk werks level 1

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.

6 months, 3 weeks

[2.2.0] Checkmk Werk 16237 created: Path to mysql.ini under Windows for mk_sql

by Checkmk werks level 1

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.

6 months, 3 weeks

[2.2.0] Checkmk Werk 16495 created: check_mailboxes: fix check of multiple mailboxes

by Checkmk werks level 1

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.

6 months, 3 weeks

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1