Checkmk werks level1

checkmk-werks-lvl1@lists.checkmk.com

1 participants
15938 discussions

[2.4.0] Checkmk Werk 16387 created: notification_rules: custom plugins now created correctly when using the REST-API

by Checkmk werks level 1

[//]: # (werk v2) # notification_rules: custom plugins now created correctly when using the REST-API key | value ---------- | --- date | 2024-01-22T08:18:31+00:00 version | 2.4.0b1 class | fix edition | cre component | rest-api level | 1 compatible | yes Previous to this werk, when creating a notification rule with a custom plugin via the rest-api, the parameters were not being shown in the UI as expected. The reason being, an incorrect format being saved to file. This werk addresses this issue by correcting the format being saved to file.

8 months

[2.4.0] Checkmk Werk 14220 created: BI: fixed exception in check if aggregation was in state PENDING

by Checkmk werks level 1

[//]: # (werk v2) # BI: fixed exception in check if aggregation was in state PENDING key | value ---------- | --- date | 2024-01-30T08:17:38+00:00 version | 2.4.0b1 class | fix edition | cre component | bi level | 1 compatible | yes

8 months

[2.4.0] Checkmk Werk 16331 created: mcafee_webgateway: Services not being discovered

by Checkmk werks level 1

[//]: # (werk v2) # mcafee_webgateway: Services not being discovered key | value ---------- | --- compatible | yes version | 2.4.0b1 date | 2024-01-29T10:17:43+00:00 level | 1 class | fix component | checks edition | cre Some mcafee services were not discovered because of the detection criteria. This has now been fixed by using the 'OBJECTID' for the detection.

8 months

[2.1.0] Checkmk Werk 16400 created: omd restart: Exit Code is 2 on Failure

by Checkmk werks level 1

Title: omd restart: Exit Code is 2 on Failure Class: fix Compatible: compat Component: omd Date: 1706275639 Edition: cre Level: 1 Version: 2.1.0p39 <code>omd restart</code> executes <code>omd start</code> and <code>omd stop</code>, both of which can terminate with exit code zero or two. Previously, the exit code of these commands would be ignored. <code>omd restart</code> now reports the worst exit code reported by the two commands.

8 months

[2.2.0] Checkmk Werk 16400 created: omd restart: Exit Code is 2 on Failure

by Checkmk werks level 1

Title: omd restart: Exit Code is 2 on Failure Class: fix Compatible: compat Component: omd Date: 1706275639 Edition: cre Level: 1 Version: 2.2.0p21 <code>omd restart</code> executes <code>omd start</code> and <code>omd stop</code>, both of which can terminate with exit code zero or two. Previously, the exit code of these commands would be ignored. <code>omd restart</code> now reports the worst exit code reported by the two commands.

8 months

[2.2.0] Checkmk Werk 16039 created: host_config: add inherited labels to effective attributes

by Checkmk werks level 1

Title: host_config: add inherited labels to effective attributes Class: fix Compatible: compat Component: rest-api Date: 1706268055 Edition: cre Level: 1 Version: 2.2.0p21 Previously, when using the effective attributes query parameter with the C+: GET /objects/host_config/{host_name} C-: endpoint, only the labels of the current host have been returned. Now all of the effective labels are aggregated and returned.

8 months

[2.4.0] Checkmk Werk 16149 created: New OderBy header in livestatus

by Checkmk werks level 1

[//]: # (werk v2) # New OderBy header in livestatus key | value ---------- | --- date | 2024-01-29T10:12:24+00:00 version | 2.4.0b1 class | feature edition | cre component | livestatus level | 1 compatible | yes We provide a new header for livestatus that returns the rows in sorted order. For example, to sort host names in descending order ``` $ lq 'GET hosts\nColumns: name\nOrderBy: name desc' zhost yhost xhost ... ``` in ascending order ``` $ lq 'GET hosts\nColumns: name\nOrderBy: name asc' ahost bhost ... ``` or, alternatively without `asc`, ``` $ lq 'GET hosts\nColumns: name\nOrderBy: name' ahost bhost ... ``` The `OrderBy` header can be combined with the `Limit` header to limit the number of results as expected. ``` $ lq 'GET hosts\nColumns: name\OrderBy: name\Limit: 1' ahost ``` Furthermore, it is possible to sort on dictionary keys with the following syntax ``` $ lq << EOF GET services Columns: host_name description performance_data OrderBy: performance_data.user_time EOF ... ```

8 months

[2.4.0] Checkmk Werk 16324 created: NetApp: addition of datasource program and check plugins for NetApp ONTAP

by Checkmk werks level 1

[//]: # (werk v2) # NetApp: addition of datasource program and check plugins for NetApp ONTAP key | value ---------- | --- date | 2024-01-29T12:15:27+00:00 version | 2.4.0b1 class | feature edition | cre component | checks level | 1 compatible | yes Since NetApp has discontinued support for their old API this werk adds datasource program and check plugins for the new NetApp ONTAP REST API. However, the new API does not provide certain metrics that were available in the old API. As a result, the new check plugins have been modified accordingly. The plugins that have been migrated with this werk are the ones that monitor: - NetApp aggregates - NetApp node's CPUs - NetApp disks - NetApp sensors of environment and shelves - NetApp node's fans - NetApp node's interfaces - NetApp LUNs - NetApp node's ports - NetApp power supply units - NetApp volumes (and snapshots) - NetApp (SVMs) Storage Virtual Machine's (formerly called "vservers”) traffic and status

8 months

[2.4.0] Checkmk Werk 16400 created: omd restart: Exit Code is 2 on Failure

by Checkmk werks level 1

[//]: # (werk v2) # omd restart: Exit Code is 2 on Failure key | value ---------- | --- date | 2024-01-26T13:27:19+00:00 version | 2.4.0b1 class | fix edition | cre component | omd level | 1 compatible | yes `omd restart` executes `omd start` and `omd stop`, both of which can terminate with exit code zero or two. Previously, the exit code of these commands would be ignored. `omd restart` now reports the worst exit code reported by the two commands.

8 months

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

8 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1