[//]: # (werk v2)
# Log to alert.log and dcd.log after logrotate
key | value
---------- | ---
compatible | yes
version | 2.4.0b1
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 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.4.0b1
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 names
+ # agent_azure: handling case insensitivity in Azure resource group names
? ++++++
key | value
---------- | ---
compatible | no
version | 2.4.0b1
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 names and resource group names aren't case sensitive.
+ 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.
- We modified the Azure agent in order to convert resources and 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)
# agent_azure: handling case insensitivity in Azure resource names
key | value
---------- | ---
compatible | no
version | 2.4.0b1
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 names and 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 and 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.
Title: Licensing: Introduce grace period for unlicensed state
Class: fix
Compatible: compat
Component: wato
Date: 1711554926
Edition: cce
Level: 1
Version: 2.2.0p27
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.
Title: cisco_temperature: Fix some CISCO-ENVMON-MIB sensors not getting discovered
Class: fix
Compatible: compat
Component: checks
Date: 1714657724
Edition: cre
Level: 1
Version: 2.2.0p27
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)
# agent_kube: resolve case when referenced PVC is no longer present
key | value
---------- | ---
date | 2024-05-06T10:47:15+00:00
version | 2.4.0b1
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 v2)
# cisco_temperature: Fix some CISCO-ENVMON-MIB sensors not getting discovered
key | value
---------- | ---
compatible | yes
version | 2.4.0b1
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)
# Fix categorization of some rule specs using new Ruleset API
key | value
---------- | ---
date | 2024-04-19T12:04:19+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
The following rule specs/topic combinations from cmk.rulesets.v1 will now be shown in different categories in the UI
* SpecialAgent with Topic.CLOUD: under `Setup > Agents > VM, cloud, container`
* AgentConfig with TOPIC.LINUX: under `Setup > Agents > Windows, Linux, Solaris, AIX > Agent rules > Linux Agent` (not available in Raw)
* AgentConfig with TOPIC.WINDOWS: under `Setup > Agents > Windows, Linux, Solaris, AIX > Agent rules > Windows Agent` (not available in Raw)
* AgentConfig with TOPIC.GENERAL: under `Setup > Agents > Windows, Linux, Solaris, AIX > Agent rules > Generic Options`
* AgentConfig with another topic: under `Setup > Agents > Windows, Linux, Solaris, AIX > Agent rules > Agent plug-ins` (not available in Raw)
[//]: # (werk v2)
# Ruleset API: SingleChoice rendering when using DictGroups
key | value
---------- | ---
date | 2024-05-03T13:31:07+00:00
version | 2.4.0b1
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.