Checkmk werks level1 May 2024

checkmk-werks-lvl1@lists.checkmk.com

1 participants
549 discussions

[2.3.0] Checkmk Werk 16525 created: password: improve the openapi documentation

by Checkmk werks level 1

[//]: # (werk v2) # password: improve the openapi documentation key | value ---------- | --- date | 2024-03-07T08:13:23+00:00 version | 2.3.0b2 class | fix edition | cre component | rest-api level | 1 compatible | yes This werk is to improve on the existing documentation for the password endpoints.

3 months, 3 weeks

[2.3.0] Checkmk Werk 16408 created: omd update: Allow Aborting Before "Completed verifying site configuration."

by Checkmk werks level 1

[//]: # (werk v2) # omd update: Allow Aborting Before "Completed verifying site configuration." key | value ---------- | --- date | 2024-03-07T13:47:39+00:00 version | 2.3.0b2 class | fix edition | cre component | omd level | 2 compatible | yes Sites may have configuration, MKPs and other local files, which are incompatible with the version targeted by `omd update`. If such a problem occurs, then aborting the update may be necessary. In earlier versions, users were advised to perform a downgrade, which was not user-friendly and had several pitfalls. Downgrading is not supported as it has many potential downsides. With this Werk, `omd update` is better able to deal with these situations. `omd update` will show the message ``` Completed verifying site configuration. Your site now has version {target version}. ``` If the update is aborted before this message is shown, then the site is restored to it's previous state. This includes selecting the `abort` option, unexpected internal errors, or aborting the update using CTRL-C.

3 months, 3 weeks

[2.3.0] Checkmk Werk 16406 created: cmk-update-config: Don't Prompt User if Using Conflict Mode "install" or "keepold"

by Checkmk werks level 1

[//]: # (werk v2) # cmk-update-config: Don't Prompt User if Using Conflict Mode "install" or "keepold" key | value ---------- | --- date | 2024-03-07T13:04:36+00:00 version | 2.3.0b2 class | fix edition | cre component | omd level | 2 compatible | yes While upgrading with `cmk-update-config`, the user can be prompted with questions about the next update steps. This questioning can be disabled by using one of the conflict options `install`, `keepold` or `abort`. Due to a regression in the 2.3.0b1 the options `install` and `keepold` do not supress these questions. In particular, if there is a problem while `Verifying the Checkmk configuration...`, then the update of Checkmk on Checkmk appliances will exit with a traceback. Upgrading to the 2.3.0b1 is thus only possible here, if all problems are fixed beforehand.

3 months, 3 weeks

[2.3.0] Checkmk Werk 16455 created: Fix metric scaling of 'rta' for Nagios plugin integration 'check_ping'

by Checkmk werks level 1

[//]: # (werk v2) # Fix metric scaling of 'rta' for Nagios plugin integration 'check_ping' key | value ---------- | --- date | 2024-03-07T15:09:07+00:00 version | 2.3.0b2 class | fix edition | cre component | multisite level | 1 compatible | yes

3 months, 3 weeks

[2.3.0] Checkmk Werk 16407 created: omd update: Don't Delete "config.pb" During Pre-Update

by Checkmk werks level 1

[//]: # (werk v2) # omd update: Don't Delete "config.pb" During Pre-Update key | value ---------- | --- date | 2024-03-07T13:27:55+00:00 version | 2.3.0b2 class | fix edition | cee component | omd level | 1 compatible | yes The `omd update` command has the capability to undo the changes it has done up until `Verifying Checkmk configuration...`. However, if any change after `Verifying Checkmk configuration...` is persisted. Due to a regression caused by Werk #15725, the file `config.pb` is deleted during this verification. If the update aborts during the verification, then users will see the following error: ``` Starting cmc...Failed (Config /omd/sites/prod_dmz/var/check_mk/core/config.pb missing, run "cmk -U" and try again) ``` With this Werk, `config.pb` will be deleting only while `Updating Checkmk configuration...`.

3 months, 3 weeks

[2.3.0] Checkmk Werk 16321 created: Fix metric history painter with inherit time range option

by Checkmk werks level 1

[//]: # (werk v2) # Fix metric history painter with inherit time range option key | value ---------- | --- compatible | yes version | 2.3.0b2 date | 2024-03-07T08:35:37+00:00 level | 1 class | fix component | reporting edition | cee If you used the option “Inherit from report time range” for the painter "Metric history" in report content elements, an error was shown in the report. This affected all previous 2.2 versions.

3 months, 3 weeks

[2.3.0] Checkmk Werk 16340 created: docker_node_images: KeyError: 'VirtualSize'

by Checkmk werks level 1

[//]: # (werk v2) # docker_node_images: KeyError: 'VirtualSize' key | value ---------- | --- compatible | yes version | 2.3.0b2 date | 2024-03-06T16:28:34+00:00 level | 1 class | fix component | checks edition | cre In newer versions of the Docker API the information about the 'VirtualSize' of a node image is not available, because it has been deprecated. From now on the plugin will use 'VirtualSize' if available, and 'Size' if not.

3 months, 3 weeks

[2.3.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.3.0b2 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

3 months, 3 weeks

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

by Checkmk werks level 1

[//]: # (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.0b2 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: */*`

3 months, 3 weeks

[2.3.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.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

3 months, 3 weeks

← Newer
1
...
35
36
37
38
39
40
41
...
55
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 May 2024