Checkmk werks level1

checkmk-werks-lvl1@lists.checkmk.com

1 participants
15936 discussions

[2.3.0] Checkmk Werk 15326 created: oracle_instance: Fix ValidationError

by Checkmk werks level 1

[//]: # (werk v2) # oracle_instance: Fix ValidationError key | value ---------- | --- date | 2024-02-05T07:35:36+00:00 version | 2.3.0b1 class | fix edition | cre component | checks level | 1 compatible | yes Both oracle instance and oracle uptime services vanished due to too strict validation. Crash report showed a `ValidationError`.

7 months, 1 week

[2.3.0] Checkmk Werk 16149 adapted: New OderBy header in livestatus

by Checkmk werks level 1

Werk 16149 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # New OderBy header in livestatus key | value ---------- | --- date | 2024-01-29T10:12:24+00:00 version | 2.3.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\nOrderBy: name\nLimit: 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 ... ``` ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) # New OderBy header in livestatus key | value ---------- | --- date | 2024-01-29T10:12:24+00:00 version | 2.3.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' + $ lq 'GET hosts\nColumns: name\nOrderBy: name\nLimit: 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 ... ```

7 months, 1 week

[2.3.0] Checkmk Werk 16402 created: azure_vm_network_io: KeyError (total_Network_In_Total)

by Checkmk werks level 1

[//]: # (werk v2) # azure_vm_network_io: KeyError (total_Network_In_Total) key | value ---------- | --- compatible | yes version | 2.3.0b1 date | 2024-02-05T14:11:34+00:00 level | 1 class | fix component | checks edition | cre The Microsoft Azure API sometimes omits the metrics total_Network_In_Total and total_Network_Out_Total. The check plugin azure_vm_network_io now omits computations based on these metrics rather than crashing.

7 months, 1 week

[2.3.0] Checkmk Werk 16315 created: Respect sort index for listed dashboards in page menu

by Checkmk werks level 1

[//]: # (werk v2) # Respect sort index for listed dashboards in page menu key | value ---------- | --- date | 2024-02-05T13:05:04+00:00 version | 2.3.0b1 class | fix edition | cre component | multisite level | 1 compatible | yes The page menu "Dashboards" in dashboards listed all other available dashboards in a random order. The defined sort index of each dashboard is now respected.

7 months, 1 week

[2.3.0] Checkmk Werk 16048 created: Import Azure tags as service labels

by Checkmk werks level 1

[//]: # (werk v2) # Import Azure tags as service labels key | value ---------- | --- date | 2024-01-29T07:26:41+00:00 version | 2.3.0b1 class | feature edition | cre component | checks level | 1 compatible | yes Azure resource tags are now imported as service labels as well. Each service that is discovered for an Azure resource now holds the resource's tags as service labels. Also, you can now restrict the import of Azure tags via regex or disable the import altogether. This can be done in the rule "Microsoft Azure" via option "Import tags as host/service labels". Note that tags are validated to 1) not hold empty values - empty values are replaced by "true" and 2) not contain colons (":") - colons are replaced by underscores ("_"). So an Azure resource tag "tag:key":"" will now be shown as "tag_key":"true".

7 months, 1 week

[2.3.0] Checkmk Werk 16047 created: Changed host labels for Azure Resource Groups and Virutal Machines

by Checkmk werks level 1

[//]: # (werk v2) # Changed host labels for Azure Resource Groups and Virutal Machines key | value ---------- | --- date | 2024-01-26T12:20:23+00:00 version | 2.3.0b1 class | feature edition | cre component | checks level | 1 compatible | no This werk affects users who use the tags of Azure Resource Groups or Virtual Machines (if monitored as hosts) as host labels in Checkmk. The host labels are renamed from the original Azure format "{key}":"{value}" to "cmk/azure/tag/{key}":"{value}" in order to stay consistent with other host labels and to avoid overwriting existing Checkmk labels. Additionally, label keys and values are now validated to 1) not hold empty values - empty values are replaced by "true" and 2) not contain colons (":") - colons are replaced by underscores ("_"). So a former label "label:key":"" will now be shown as "label_key":"true". The old labels will be removed in version 2.4.0.

7 months, 1 week

[2.3.0] Checkmk Werk 16333 created: if_lancom: Switch port discovery does not work for Lancom routers when the router description is configured to be used for the Service Description

by Checkmk werks level 1

[//]: # (werk v2) # if_lancom: Switch port discovery does not work for Lancom routers when the router description is configured to be used for the Service Description key | value ---------- | --- date | 2024-02-01T16:48:01+00:00 version | 2.3.0b1 class | fix edition | cre component | checks level | 1 compatible | no Sometimes the Lancom routers don't provide a name. During data parsing this caused the description to be left as an empty string. As a result of that, when the router description was configured to be used for the Service Desciption, the discovery did not work properly. This has now been fixed by having a fallback mechanism. If the router name is not present, the router description will be used. Because of the change, the user is required to execute the service discovery again in order to discover any new services. As well as get rid of any vanished services.

7 months, 1 week

[2.3.0] Checkmk Werk 16401 created: omd start mkeventd: Error Code of Event Daemon

by Checkmk werks level 1

[//]: # (werk v2) # omd start mkeventd: Error Code of Event Daemon key | value ---------- | --- date | 2024-02-02T12:32:48+00:00 version | 2.3.0b1 class | fix edition | cre component | omd level | 1 compatible | yes The command `omd start mkeventd` starts the event daemon. Previously, any exit code produced by this daemon would be ignored. Now, if the exit code is non-zero, then the message `Failed` is shown and the command `omd start mkeventd` exits with error code 2.

7 months, 1 week

[2.3.0] Checkmk Werk 16471 created: Hide private topics in dropdowns

by Checkmk werks level 1

[//]: # (werk v2) # Hide private topics in dropdowns key | value ---------- | --- date | 2024-02-01T08:07:44+00:00 version | 2.3.0b1 class | fix edition | cre component | multisite level | 1 compatible | yes Private topics were showing up in dropdowns (e.g. when editing dashboards). Now they are hidden if the user does not have permissions for them.

7 months, 1 week

[2.3.0] Checkmk Werk 16470 created: Fix topics being falsely shown as public

by Checkmk werks level 1

[//]: # (werk v2) # Fix topics being falsely shown as public key | value ---------- | --- date | 2024-02-01T08:01:39+00:00 version | 2.3.0b1 class | fix edition | cre component | multisite level | 1 compatible | no Previously, pagetypes (bookmarks, custom graphs, topics etc.) were falsely handled as public, rather than private. Items published only to specific groups are not affected and were handled correctly. This change may cause users to no longer see public overwrites by admins for example. Please ensure your permissions and publish states are configured correctly.

7 months, 1 week

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1