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.
Title: mssql_datafiles/transactionlogs: Regression in maximum size calculation
Class: fix
Compatible: compat
Component: checks
Date: 1694589964
Edition: cre
Level: 1
Version: 2.2.0p25
This is a follow-up to Werk #14421.
Since Checkmk 2.1.0p5, we calculate the maximum size as the sum of available
and used size for unlimited instances.
However, in some cases, we accidentally drop explicit thresholds for the
maximum size if avaiable, falling back to the unlimited case.
[//]: # (werk v2)
# Ruleset API: Rename PredictiveLevels.prefill_stddev_diff to prefill_stdev_diff
key | value
---------- | ---
date | 2024-04-08T14:16:32+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | no
This change is only relevant for plugin developers.
Werk 15515 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# check_http: Soft deprecatation of old HTTP monitoring plug-in
key | value
---------- | ---
date | 2024-04-03T13:15:48+00:00
version | 2.4.0b1
class | feature
edition | cre
component | checks
level | 2
compatible | no
The old plug-in is being deprecated in a soft way with this werk. Unlike
hard deprecation, the deprecated rule set "Check HTTP service" will remain
fully functional. However, new rules should only be created if absolutely
necessary, such as when experiencing issues with the new "Check HTTP web
service" implementation and needing to roll back to the old one.
Please note that the rule set will be hard deprecated in version 2.4.0,
meaning that you will no longer be able to create new rules. However, the
plug-in itself will remain available as this is a component of the
monitoring-plugins collection that comes with Checkmk.
Please let us know if you find any features that were present in the old
plug-in but are missing in the new one.
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
# check_http: Soft deprecatation of old HTTP monitoring plug-in
key | value
---------- | ---
date | 2024-04-03T13:15:48+00:00
version | 2.4.0b1
class | feature
edition | cre
component | checks
level | 2
compatible | no
The old plug-in is being deprecated in a soft way with this werk. Unlike
hard deprecation, the deprecated rule set "Check HTTP service" will remain
fully functional. However, new rules should only be created if absolutely
necessary, such as when experiencing issues with the new "Check HTTP web
service" implementation and needing to roll back to the old one.
Please note that the rule set will be hard deprecated in version 2.4.0,
meaning that you will no longer be able to create new rules. However, the
plug-in itself will remain available as this is a component of the
monitoring-plugins collection that comes with Checkmk.
- Please know us know if you find any features that were present in the old
? --------
+ Please let us know if you find any features that were present in the old
? +++++++
plug-in but are missing in the new one.
[//]: # (werk v2)
# jolokia_info: Support Version 2.0
key | value
---------- | ---
date | 2024-04-08T09:28:55+00:00
version | 2.4.0b1
class | feature
edition | cre
component | checks
level | 1
compatible | yes
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 `jolokia_info` showed
`unknown` instead of the product information. After updating the agent plugin `mk_jolokia.py`, the
correct information will be shown again.