Checkmk werks level1

checkmk-werks-lvl1@lists.checkmk.com

1 participants
15927 discussions

[2.4.0] Checkmk Werk 16457 created: cisco_meraki: Add host labels

by Checkmk werks level 1

[//]: # (werk v2) # cisco_meraki: Add host labels key | value ---------- | --- date | 2024-03-12T12:19:42+00:00 version | 2.4.0b1 class | feature edition | cre component | checks level | 1 compatible | yes cmk/meraki: This label is set to "yes" for all Meraki devices cmk/meraki/device_type: This label is set to the Meraki product type to which the device belongs, such as "switch" or "wireless". cmk/meraki/net_id: This label is set to the network id the Meraki device belongs to. cmk/meraki/org_id: This label is set to the organisation id the Meraki device belongs to. cmk/meraki/org_name: This label is set to the organisation name the Meraki device belongs to.

6 months, 2 weeks

[2.4.0] Checkmk Werk 16380 created: Ruleset API: add option to configure the default levels type

by Checkmk werks level 1

[//]: # (werk v2) # Ruleset API: add option to configure the default levels type key | value ---------- | --- date | 2024-03-11T13:21:51+00:00 version | 2.4.0b1 class | feature edition | cre component | checks level | 1 compatible | yes For details refer to the developer documentation in your sites "Help" menu.

6 months, 2 weeks

[2.4.0] Checkmk Werk 16322 created: Show used filter of virtual host tree

by Checkmk werks level 1

[//]: # (werk v2) # Show used filter of virtual host tree key | value ---------- | --- compatible | yes version | 2.4.0b1 date | 2024-03-08T13:45:32+00:00 level | 1 class | fix component | multisite edition | cre If you opened the "Filter" option of a view that was visited via a link from the "Virtual host tree" snapin, all filters were empty.

6 months, 2 weeks

[2.4.0] Checkmk Werk 16381 created: HP-UX: Mirror State of LVM Logical Volumes: be more robust in state evaluation

by Checkmk werks level 1

[//]: # (werk v2) # HP-UX: Mirror State of LVM Logical Volumes: be more robust in state evaluation key | value ---------- | --- date | 2024-03-11T13:39:19+00:00 version | 2.4.0b1 class | feature edition | cre component | checks level | 1 compatible | yes The plugin previously only considered the status to be OK if the device reported a literal "available,syncd". It now is OK for any combination of (some of) the words "available", "syncd", "snapshot" and "space_efficient".

6 months, 2 weeks

[2.4.0] Checkmk Werk 16501 adapted: introduce command to start openapi-spec generation background job

by Checkmk werks level 1

Werk 16501 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # introduce command to start openapi-spec generation background job key | value ---------- | --- date | 2024-02-29T13:06:16+00:00 version | 2.4.0b1 class | feature edition | cre component | rest-api 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 introduces a command to trigger the background job for the regeneration of the API specification. 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. ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) - # omd: trigger openapi-spec generation job during start, restart and reload + # introduce command to start openapi-spec generation background job key | value ---------- | --- date | 2024-02-29T13:06:16+00:00 version | 2.4.0b1 class | feature edition | cre - component | omd + component | rest-api 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, ? ^ ^^^ ^^^^ ------- + potential time required for completion. This update introduces a command ? ^^^^ ^^ ^^^ +++ - restart, and reload commands to initiate this specific background job upon + to trigger the background job for the regeneration of the API specification. - execution. Users should be aware that triggering the job does not result ? ----------- + 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 ? ^^^^^^^^ + to trigger and wait for the specification regeneration manually. ? ^ - 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, 2 weeks

[2.4.0] Checkmk Werk 16320 created: Publish permission handling

by Checkmk werks level 1

[//]: # (werk v2) # Publish permission handling key | value ---------- | --- compatible | no version | 2.4.0b1 date | 2024-03-05T12:32:34+00:00 level | 1 class | fix component | multisite edition | cre Werk 13498 introduced the possibility to set publish permissions independently of each other. Still, the permission "Publish views" (e.g. for publishing views) was needed to see the published views. This has been fixed. Note: Please check your publish configuration in views, dashboards, etc.

6 months, 2 weeks

[2.4.0] Checkmk Werk 16485 created: host_config: Create hosts in folder with umlauts

by Checkmk werks level 1

[//]: # (werk v2) # host_config: Create hosts in folder with umlauts key | value ---------- | --- date | 2024-03-11T12:51:50+00:00 version | 2.4.0b1 class | fix edition | cre component | rest-api level | 1 compatible | yes When creating hosts in a folder with umlauts in the name via one of the `host_config` endpoints the endpoint would return an error 400 even though the query was correct. Now the hosts are created correctly.

6 months, 2 weeks

[2.4.0] Checkmk Werk 16621 created: Ruleset API: Remove TupleDoNotUseWillbeRemoved from API

by Checkmk werks level 1

[//]: # (werk v2) # Ruleset API: Remove TupleDoNotUseWillbeRemoved from API key | value ---------- | --- date | 2024-03-11T13:47:41+00:00 version | 2.4.0b1 class | fix edition | cre component | wato level | 1 compatible | no As the name indicates, the previous `Tuple` FormSpec should no longer be used and with this will no longer be available in the API. Use `SimpleLevels` or `Levels` instead if you want to configure levels or a `Dictionary` otherwise.

6 months, 2 weeks

[2.1.0] Checkmk Werk 16447 created: Fix inventory sync of subsequent hosts if a previous one has invalid data

by Checkmk werks level 1

Title: Fix inventory sync of subsequent hosts if a previous one has invalid data Class: fix Compatible: compat Component: liveproxy Date: 1707132754 Edition: cee Level: 1 Version: 2.1.0p41

6 months, 2 weeks

[2.1.0] Checkmk Werk 16448 created: Fix inventory sync of hosts if remote data is updated at the time when liveproxyd sync starts or ends

by Checkmk werks level 1

Title: Fix inventory sync of hosts if remote data is updated at the time when liveproxyd sync starts or ends Class: fix Compatible: compat Component: liveproxy Date: 1707132975 Edition: cee Level: 1 Version: 2.1.0p41 When the liveproxyd starts or ends at a particular time TS and remote inventory data is written between TS and \<TS+1 then it's not synced.

6 months, 2 weeks

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1