[//]: # (werk v2)
# netapp_ontap_info: enhanced presentation of NetApp system information
key | value
---------- | ---
date | 2024-02-15T10:04:03+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
The version and hardware information for a NetApp system was only displayed for the first retrieved node.
With this werk we now display information for each retrieved node.
[//]: # (werk v2)
# bi_rule: schema update to match the api docs
key | value
---------- | ---
date | 2024-02-19T14:34:33+00:00
version | 2.4.0b1
class | fix
edition | cre
component | rest-api
level | 1
compatible | no
The Open API schema previously did not reflect the response or the request
schema format that was required to create or show BI rules. This werk
addresses this issue.
Previously, when creating or getting a BI rule, via the REST-API, the
schema for host_label_groups or service_label_groups looked similar
to the following:
```
"host_label_groups": [
[
"and",
[
["and", "mystery/switch:yes"],
["or", "mystery/switch:no"],
],
],
]
```
This did not match the schema documented in the Open API docs.
To fix this, we have now changed the format to the following
```
"host_label_groups": [
{
"operator": "and",
"label_group": [
{"operator": "and", "label": "mystery/switch:yes"},
{"operator": "or", "label": "mystery/switch:no"},
],
},
]
```
This also aligns with other endpoints that use our new
host_label_groups or service_label_groups, for example the
rules endpoints.
As this is a breaking change, user scripts should be adjusted
accordingly.
[//]: # (werk v2)
# aws: Fix Cloudwatch alarms fetching
key | value
---------- | ---
compatible | yes
version | 2.4.0b1
date | 2024-02-21T13:16:55+00:00
level | 1
class | fix
component | checks
edition | cre
Cloudwatch alarms weren't fetched properly for environments with a lot
of alarms. It resulted in missing alarms in the 'AWS/CloudWatch Alarms' service.
Title: Regression when obtaining mails from mailbox
Class: fix
Compatible: compat
Component: checks
Date: 1708521462
Edition: cre
Level: 1
Version: 2.2.0p23
This regression exists since 2.2.0b1. Monitoring mails in your in box may have not been possible.
This is fixed now.
[//]: # (werk v2)
# Regression when obtaining mails from mailbox
key | value
---------- | ---
compatible | yes
version | 2.3.0b1
date | 2024-02-21T13:17:42+00:00
level | 1
class | fix
component | checks
edition | cre
This regression exists since 2.2.0b1. Monitoring mails in your in box may have not been possible.
This is fixed now.
[//]: # (werk v2)
# aws: Fix Cloudwatch alarms fetching
key | value
---------- | ---
compatible | yes
version | 2.3.0b1
date | 2024-02-21T13:16:55+00:00
level | 1
class | fix
component | checks
edition | cre
Cloudwatch alarms weren't fetched properly for environments with a lot
of alarms. It resulted in missing alarms in the 'AWS/CloudWatch Alarms' service.
[//]: # (werk v2)
# aws: Inventorization of EC2 and ELB tags as host labels
key | value
---------- | ---
date | 2024-02-21T11:56:07+00:00
version | 2.3.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
There was a problem during service discovery which prevented Checkmk
from assigning the AWS EC2 and ELB tags delivered by the AWS agent to
their respective piggyback hosts. This werk fixes the discovery process
such that the data is parsed properly and custom tags from AWS will
now show up as host labels on the created piggyback hosts.
[//]: # (werk v2)
# Checkmk Linux agent: ignore \*.dpkg-tmp files in plugin folder
key | value
---------- | ---
date | 2024-02-20T21:25:44+00:00
version | 2.3.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
The Checkmk agents for Linux, Solaris, AIX, OpenWrt and FreeBSD now ignore \*.dpkg-tmp files in the plugins folder.
They previously executed them inadvertedly as plugins.
This mostly fails silently (or even succeedes), but sometimes it is reported by the "Check_MK Agent" service.