[//]: # (werk v2)
# HW-/SW-Inventory: Do not run autoinventory for inventorized hosts
key | value
---------- | ---
compatible | yes
version | 2.4.0b1
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.
Title: HW-/SW-Inventory: Do not run autoinventory for inventorized hosts
Class: fix
Compatible: compat
Component: inv
Date: 1712740134
Edition: cre
Level: 1
Version: 2.2.0p25
Previously hosts marked for inventorization were afterwards not unmarked, meaning they would be processed again everytime the autoinventory was running.
This has been fixed.
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.4.0b1
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.4.0b1
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.
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.4.0b1
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.4.0b1
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.
[//]: # (werk v2)
# Synthetic Monitoring: Adopt 'Plan' Naming Convention
key | value
---------- | ---
date | 2024-04-09T11:39:57+00:00
version | 2.4.0b1
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.
[//]: # (werk v2)
# REST API: add mode parameter to host tag group delete endpoint
key | value
---------- | ---
date | 2024-04-09T12:01:49+00:00
version | 2.4.0b1
class | feature
edition | cre
component | rest-api
level | 1
compatible | yes
This werk adds the `mode` query parameter to the delete endpoint for host tag
groups. It is an alternative to the existing `repair` parameter, with the
following options:
* `mode=abort` default behaviour, cancel deletion if tag group is in use
* `mode=delete` same as `repair=True`, will delete affected rules
* `mode=remove` will remove the tag group condition from rules instead of
deleting the entire rule
Title: jolokia_info: Support Version 2.0
Class: feature
Compatible: compat
Component: checks
Date: 1712568535
Edition: cre
Level: 1
Version: 2.2.0p25
Jolokia 2.0 was released 2023-12-19. With the release some changes to the Jolokia Protocol have been
introduced. If a user installed this version of Jolokia, the check plugin <code>jolokia_info</code> showed
<code>unknown</code> instead of the product information. After updating the agent plugin <code>mk_jolokia.py</code>, the
correct information will be shown again.