Checkmk werks level1 May 2024

checkmk-werks-lvl1@lists.checkmk.com

1 participants
549 discussions

[2.3.0] Checkmk Werk 16587 created: tags: Prevent builtin auxiliary tags and host tag groups override

by Checkmk werks level 1

[//]: # (werk v2) # tags: Prevent builtin auxiliary tags and host tag groups override key | value ---------- | --- date | 2024-04-09T11:57:18+00:00 version | 2.3.0b5 class | fix edition | cre component | wato level | 1 compatible | yes Before this Werk it was possible to create auxiliary tags with the same name as a host tag group and vice versa. This Werk adds an additional check when creating such elements, both in WATO and in the REST API.

3 months, 3 weeks

[2.3.0] Checkmk Werk 16694 created: Fix event statistics dashlet filters

by Checkmk werks level 1

[//]: # (werk v2) # Fix event statistics dashlet filters key | value ---------- | --- compatible | yes version | 2.3.0b5 date | 2024-04-09T09:59:29+00:00 level | 1 class | fix component | multisite edition | cre For the dashlet "Event statistics" you were able to configure "Host" and "Service" Context/Search filter. The "Service" filter had no effect and is now replaced with the "Event Console event" filter option.

3 months, 3 weeks

[2.3.0] Checkmk Werk 16678 created: HW-/SW-Inventory: Do not run autoinventory for inventorized hosts

by Checkmk werks level 1

[//]: # (werk v2) # HW-/SW-Inventory: Do not run autoinventory for inventorized hosts key | value ---------- | --- compatible | yes version | 2.3.0b5 date | 2024-04-10T09:08:54+00:00 level | 1 class | fix component | inv edition | cre Previously hosts marked for inventorization were afterwards not unmarked, meaning they would be processed again everytime the autoinventory was running. This has been fixed.

3 months, 3 weeks

[2.3.0] Checkmk Werk 16685 created: emcvnx_info: Fix regression in 2.3.0-beta

by Checkmk werks level 1

[//]: # (werk v2) # emcvnx_info: Fix regression in 2.3.0-beta key | value ---------- | --- date | 2024-04-10T14:54:18+00:00 version | 2.3.0b5 class | fix edition | cre component | checks level | 1 compatible | yes

3 months, 3 weeks

[2.3.0] Checkmk Werk 16462 created: Fix empty HW/SW inventory history

by Checkmk werks level 1

[//]: # (werk v2) # Fix empty HW/SW inventory history key | value ---------- | --- date | 2024-04-11T12:30:37+00:00 version | 2.3.0b5 class | fix edition | cre component | inv level | 1 compatible | yes

3 months, 3 weeks

[2.3.0] Checkmk Werk 16552 adapted: Crash on activate changes when re-registering agents

by Checkmk werks level 1

Werk 16552 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # Crash on activate changes when re-registering agents key | value ---------- | --- date | 2024-03-28T15:50:10+00:00 version | 2.3.0b5 class | fix edition | cre component | checks level | 1 compatible | yes When re-registering agents, a call to activate changes could crash with an error message like ``` [Errno 2] No such file or directory: '/omd/sites/<site>/var/agent-receiver/received-outputs/<uuid> ``` ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) # Crash on activate changes when re-registering agents key | value ---------- | --- date | 2024-03-28T15:50:10+00:00 - version | 2.3.0b4 ? ^ + version | 2.3.0b5 ? ^ class | fix edition | cre component | checks level | 1 compatible | yes When re-registering agents, a call to activate changes could crash with an error message like ``` [Errno 2] No such file or directory: '/omd/sites/<site>/var/agent-receiver/received-outputs/<uuid> ```

3 months, 3 weeks

[2.3.0] Checkmk Werk 16421 adapted: Synthetic Monitoring: Adopt 'Plan' Naming Convention

by Checkmk werks level 1

Werk 16421 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # Synthetic Monitoring: Adopt 'Plan' Naming Convention key | value ---------- | --- date | 2024-04-09T11:39:57+00:00 version | 2.3.0b5 class | fix edition | cee component | checks level | 1 compatible | no This Werk affects users, who have configured the rule `Robotmk Scheduler (Windows)` during the 2.3.0 beta. The naming conventions of the check plugin `robotmk_suite` have been reworked. * Plugin was renamed from `robotmk_suite` to `robotmk_plan`. * Service label value changed from `cmk/rmk/type:suite` to `cmk/rmk/type:plan`. * The service item has changed it's suffix from `Suite` to `Plan`. * The metric was renamed from `robotmk_suite_runtime` to `robotmk_peak_attempt_runtime` * The metric was renamed from `robotmk_runtime_timeout_ratio` to `robotmk_runtime_limit_ratio` Users affected by this change must run re-discovery. ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) # Synthetic Monitoring: Adopt 'Plan' Naming Convention key | value ---------- | --- date | 2024-04-09T11:39:57+00:00 version | 2.3.0b5 class | fix edition | cee component | checks level | 1 compatible | no This Werk affects users, who have configured the rule `Robotmk Scheduler (Windows)` during the 2.3.0 beta. The naming conventions of the check plugin `robotmk_suite` have been reworked. * Plugin was renamed from `robotmk_suite` to `robotmk_plan`. * Service label value changed from `cmk/rmk/type:suite` to `cmk/rmk/type:plan`. * The service item has changed it's suffix from `Suite` to `Plan`. + * The metric was renamed from `robotmk_suite_runtime` to `robotmk_peak_attempt_runtime` + * The metric was renamed from `robotmk_runtime_timeout_ratio` to `robotmk_runtime_limit_ratio` Users affected by this change must run re-discovery.

3 months, 3 weeks

[2.3.0] Checkmk Werk 16421 adapted: Synthetic Monitoring: Adopt 'Plan' Naming Convention

by Checkmk werks level 1

Werk 16421 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # Synthetic Monitoring: Adopt 'Plan' Naming Convention key | value ---------- | --- date | 2024-04-09T11:39:57+00:00 version | 2.3.0b5 class | fix edition | cee component | checks level | 1 compatible | no This Werk affects users, who have configured the rule `Robotmk Scheduler (Windows)` during the 2.3.0 beta. The naming conventions of the check plugin `robotmk_suite` have been reworked. * Plugin was renamed from `robotmk_suite` to `robotmk_plan`. * Service label value changed from `cmk/rmk/type:suite` to `cmk/rmk/type:plan`. * The service item has changed it's suffix from `Suite` to `Plan`. Users affected by this change must run re-discovery. ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) # Synthetic Monitoring: Adopt 'Plan' Naming Convention key | value ---------- | --- date | 2024-04-09T11:39:57+00:00 version | 2.3.0b5 class | fix edition | cee component | checks level | 1 compatible | no This Werk affects users, who have configured the rule `Robotmk Scheduler (Windows)` during the 2.3.0 beta. The naming conventions of the check plugin `robotmk_suite` have been reworked. - * Plugin was renamed from `robotmk_suite` to `robotmk_plan` + * Plugin was renamed from `robotmk_suite` to `robotmk_plan`. ? + * Service label value changed from `cmk/rmk/type:suite` to `cmk/rmk/type:plan`. + * The service item has changed it's suffix from `Suite` to `Plan`. Users affected by this change must run re-discovery.

3 months, 3 weeks

[2.3.0] Checkmk Werk 16421 created: Synthetic Monitoring: Adopt 'Plan' Naming Convention

by Checkmk werks level 1

[//]: # (werk v2) # Synthetic Monitoring: Adopt 'Plan' Naming Convention key | value ---------- | --- date | 2024-04-09T11:39:57+00:00 version | 2.3.0b5 class | fix edition | cee component | checks level | 1 compatible | no This Werk affects users, who have configured the rule `Robotmk Scheduler (Windows)` during the 2.3.0 beta. The naming conventions of the check plugin `robotmk_suite` have been reworked. * Plugin was renamed from `robotmk_suite` to `robotmk_plan` * Service label value changed from `cmk/rmk/type:suite` to `cmk/rmk/type:plan`. Users affected by this change must run re-discovery.

3 months, 3 weeks

[2.3.0] Checkmk Werk 15026 adapted: Disallow python_plugins and lnx_remote_alert_handlers agent config options for users without the "add_or_modify_executables" permission

by Checkmk werks level 1

Werk 15026 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # Disallow python_plugins and lnx_remote_alert_handlers agent config options for users without the "add_or_modify_executables" permission key | value ---------- | --- date | 2024-03-15T10:37:41+00:00 version | 2.3.0b4 class | fix edition | cre component | wato level | 1 compatible | yes Without the "add_or_modify_executables" permission users do not have the right to change any executable run by checkmk, either on the site or via the agent. The agent config options "python_plugins" and "lnx_remote_alert_handlers" have not yet checked for that permission. In the UI "python_plugins" and "lnx_remote_alert_handlers are called "Python agent plugin execution (UNIX)" and "Remote alert handler (Linux)" respectively. ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) # Disallow python_plugins and lnx_remote_alert_handlers agent config options for users without the "add_or_modify_executables" permission key | value ---------- | --- date | 2024-03-15T10:37:41+00:00 - version | 2.3.0b5 ? ^ + version | 2.3.0b4 ? ^ class | fix edition | cre component | wato level | 1 compatible | yes Without the "add_or_modify_executables" permission users do not have the right to change any executable run by checkmk, either on the site or via the agent. The agent config options "python_plugins" and "lnx_remote_alert_handlers" have not yet checked for that permission. In the UI "python_plugins" and "lnx_remote_alert_handlers are called "Python agent plugin execution (UNIX)" and "Remote alert handler (Linux)" respectively.

3 months, 3 weeks

← Newer
1
...
19
20
21
22
23
24
25
...
55
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 May 2024