[//]: # (werk v2)
# Fix unescaped details for process discovery checks in availability
key | value
---------- | ---
compatible | yes
version | 2.3.0p2
date | 2024-05-07T07:53:43+00:00
level | 1
class | fix
component | multisite
edition | cre
Werk #15523 introduced a change in the escaping of ps checks but the
availability still showed a broken table.
This is fixed now.
[//]: # (werk v2)
# Log to alert.log and dcd.log after logrotate
key | value
---------- | ---
compatible | yes
version | 2.3.0p2
date | 2024-05-07T09:32:55+00:00
level | 1
class | fix
component | wato
edition | cee
Same as werk #16700 and #16698 for alert.log and dcd.log.
[//]: # (werk v2)
# agent_kube: resolve case when referenced PVC is no longer present
key | value
---------- | ---
date | 2024-05-06T10:47:15+00:00
version | 2.3.0p2
class | fix
edition | cre
component | checks
level | 1
compatible | yes
Prior to this werk, the Kubernetes special agent failed whenever
the API returned Kubernetes objects with at least one reference
to a no longer existing PVC. This werk fixes this issue by ignoring
such references.
Werk 16761 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# agent_azure: handling case insensitivity in Azure resource group names
key | value
---------- | ---
compatible | no
version | 2.3.0p2
date | 2024-04-23T08:25:11+00:00
level | 1
class | fix
component | checks
edition | cre
This change impacts all those who are monitoring Azure systems.
Azure resource group names aren't case sensitive.
The APIs may return values with different casing than the originally specified name.
(see: https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/f…)
We modified the Azure agent in order to convert resources groups to lower case as soon as they are retrieved from the api.
This is an incompatible change so a rediscovery is needed for the services to be properly monitored.
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
# agent_azure: handling case insensitivity in Azure resource group names
key | value
---------- | ---
compatible | no
- version | 2.3.0p1
? ^
+ version | 2.3.0p2
? ^
date | 2024-04-23T08:25:11+00:00
level | 1
class | fix
component | checks
edition | cre
This change impacts all those who are monitoring Azure systems.
Azure resource group names aren't case sensitive.
The APIs may return values with different casing than the originally specified name.
(see: https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/f…)
We modified the Azure agent in order to convert resources groups to lower case as soon as they are retrieved from the api.
This is an incompatible change so a rediscovery is needed for the services to be properly monitored.
[//]: # (werk v2)
# Correctly disable async mode mk-sql plugin config
key | value
---------- | ---
date | 2024-05-07T14:56:50+00:00
version | 2.3.0p2
class | fix
edition | cre
component | checks
level | 1
compatible | yes
Previously, it was not possible to disable async
mode for sections that were async by default.
Since this release, the problem has been fixed.
[//]: # (werk v2)
# agent_azure: handling case insensitivity in Azure resource group names
key | value
---------- | ---
compatible | no
version | 2.3.0p1
date | 2024-04-23T08:25:11+00:00
level | 1
class | fix
component | checks
edition | cre
This change impacts all those who are monitoring Azure systems.
Azure resource group names aren't case sensitive.
The APIs may return values with different casing than the originally specified name.
(see: https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/f…)
We modified the Azure agent in order to convert resources groups to lower case as soon as they are retrieved from the api.
This is an incompatible change so a rediscovery is needed for the services to be properly monitored.
[//]: # (werk v2)
# Windows agent internal users are permanent now
key | value
---------- | ---
date | 2024-05-07T09:18:50+00:00
version | 2.3.0p2
class | fix
edition | cre
component | checks
level | 1
compatible | yes
Previously, the Windows agent service deleted internal users
created to execute plugins in group mode. As a result, the
permission list for certain files may look strange over time,
filled with UUIDs of non-existent users.
With this release, the problem has been resolved. The agent
will create or reuse an existing user and will not delete it
[//]: # (werk v2)
# cisco_temperature: Fix some CISCO-ENVMON-MIB sensors not getting discovered
key | value
---------- | ---
compatible | yes
version | 2.3.0p1
date | 2024-05-02T13:48:44+00:00
level | 1
class | fix
component | checks
edition | cre
There was a bug in how temperature sensors from Cisco devices using
<code>CISCO-ENVMON-MIB</code> were parsed which stopped them from being
discovered.
This werk fixes the bug, allowing all cisco temperature sensors using
that MIB to be discovered.
[//]: # (werk v2)
# Licensing: Introduce grace period for unlicensed state
key | value
---------- | ---
date | 2024-03-27T15:55:26+00:00
version | 2.3.0p1
class | fix
edition | cce
component | wato
level | 1
compatible | yes
To lessen the impact of a setup becoming unlicensed, there is now a 7 day grace period before becoming unlicensed.
In this time only warnings will be shown so that users have the opportunity to fix the licensing issues.
[//]: # (werk v2)
# Ruleset API: SingleChoice rendering when using DictGroups
key | value
---------- | ---
date | 2024-05-03T13:31:07+00:00
version | 2.3.0p1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
When a SingleChoice (rendered as a Dropdown) is grouped together with another element via a DictGroup, the Dropdown could not be closed after opening it.
This affected the "cert" ruleset of the shipped rulesets.