[//]: # (werk v2)
# Fixed stuck activate changes on bulk discovery and when using the DCD
key | value
---------- | ---
date | 2024-03-08T13:17:45+00:00
version | 2.4.0b1
class | fix
edition | cme
component | wato
level | 1
compatible | yes
Activate changes stopped working when initiating a bulk discovery or using the DCD with automatic service discovery.
Werk 16619 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# Ruleset API: Ruleset validation
key | value
---------- | ---
date | 2024-03-11T12:46:16+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | no
Rulespec/ruleset names now have to be valid [python identifiers](https://docs.python.org/3/reference/lexical_analysis.html#iden….
The validation occurs during instantiation and will raise a `ValueError` when a violation is found.
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
# Ruleset API: Ruleset validation
key | value
---------- | ---
date | 2024-03-11T12:46:16+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | no
Rulespec/ruleset names now have to be valid [python identifiers](https://docs.python.org/3/reference/lexical_analysis.html#iden….
The validation occurs during instantiation and will raise a `ValueError` when a violation is found.
-
[//]: # (werk v2)
# Ruleset API: Ruleset validation
key | value
---------- | ---
date | 2024-03-11T12:46:16+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | no
Rulespec/ruleset names now have to be valid [python identifiers](https://docs.python.org/3/reference/lexical_analysis.html#iden….
The validation occurs during instantiation and will raise a `ValueError` when a violation is found.
Title: jolokia metrics: restores 'default product' behavior
Class: fix
Compatible: compat
Component: checks
Date: 1710165014
Edition: cre
Level: 1
Version: 2.1.0p41
The check plugin no longer showed any metrics if a product was not specified in the ruleset configuration.
This werk restores the original behaviour, using as a default product the one reported in the info section of the agent output.
Title: netapp_ontap_temp: restore check of list of sensors
Class: fix
Compatible: compat
Component: checks
Date: 1708967815
Edition: cre
Level: 1
Version: 2.2.0p24
The above-mentioned plugin now monitors the list of ambient and internal temperature sensors,
sticking to the logic of the netapp_api_temp plugin (old Netapp API).
A re-discovery is needed to monitor the new services.
Werk 16114 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: folder_config: Extend GET and DELETE endpoints folder name pattern to match the CREATE enpoint one
Class: fix
Compatible: compat
Component: rest-api
Date: 1696846527
Edition: cre
Level: 1
Version: 2.2.0p24
Prior to this Werk, the folder name pattern for GET and DELETE endpoints did not allow the use of unicode characters while they were supported by the CREATE endpoint, with the result that folders created with such characters could not be accessed or deleted from the REST API.
For example, the user was able to create a folder named û亿Ï8Ĺ, which then could not be read or deleted from the API.
This Werk widens the folder name pattern on GET and DELETE endpoints to align with the CREATE one and now all of them support unicode characters.
------------------------------------<diff>-------------------------------------------
Title: folder_config: Extend GET and DELETE endpoints folder name pattern to match the CREATE enpoint one
Class: fix
Compatible: compat
Component: rest-api
Date: 1696846527
Edition: cre
Level: 1
Version: 2.2.0p24
- Previously, the folder name pattern for GET and DELETE endpoints were stricter than the CREATE, provoking that a new folder could not be retrieved nor deleted. This fix widens the folder name pattern on GET and DELETE endpoints to align with the CREATE one.
+ Prior to this Werk, the folder name pattern for GET and DELETE endpoints did not allow the use of unicode characters while they were supported by the CREATE endpoint, with the result that folders created with such characters could not be accessed or deleted from the REST API.
+ For example, the user was able to create a folder named û亿Ï8Ĺ, which then could not be read or deleted from the API.
+
+ This Werk widens the folder name pattern on GET and DELETE endpoints to align with the CREATE one and now all of them support unicode characters.
+
+
Title: agent_azure: fix parsing loadbalancer data
Class: fix
Compatible: compat
Component: checks
Date: 1709739981
Edition: cre
Level: 1
Version: 2.2.0p24
The agent would crash if information (backend pools or outbound rules) was missing for a load balancer.
This werk ensures that the system handles scenarios where this data may not be present.