Title: EC: improve handling of non-UTF-8 characters in messages
Class: fix
Compatible: compat
Component: ec
Date: 1708674008
Edition: cee
Level: 1
Version: 2.2.0p23
Previously, the Event Console would show an error such as
"UnicodeDecodeError: 'utf-8' codec can't decode byte 0x80 in position 0: invalid start byte"
when trying to process a message that contained non-UTF-8 characters.
With this werk, the EC no longer crashes.
Any non-UTF-8 sequence of bytes is replaced with U+FFFD,
the standard Unicode replacement character for an unrecognized character.
[//]: # (werk v2)
# EC: fix a wrong message on a matched rule
key | value
---------- | ---
date | 2024-02-23T08:14:30+00:00
version | 2.4.0b1
class | fix
edition | cee
component | ec
level | 1
compatible | yes
Previously, the tooltip on a matched rule would say it is a cancelling rule.
This message was misleading and was changed.
[//]: # (werk v2)
# snmp: Store OID cache per context group
key | value
---------- | ---
compatible | yes
version | 2.4.0b1
date | 2024-02-07T09:54:40+00:00
level | 1
class | fix
component | checks
edition | cre
SNMP caching didn't take contexts in consideration when storing
OID data. This led to the same result being reported for the OID
in different sections even if sections use different contexts.
Now, SNMP caching stores fetched OID data for every group of contexts
it was called with.
Title: aws: Inventorization of EC2 and ELB tags as host labels
Class: fix
Compatible: compat
Component: checks
Date: 1708516567
Edition: cre
Level: 1
Version: 2.1.0p40
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 16404 was deleted. The following Werk is no longer relevant.
Title: omd cp: Fix etc/ssl/agents/legacy_ca.pem Points to Source of Copy
Class: fix
Compatible: compat
Component: omd
Date: 1707904094
Edition: cre
Level: 1
Version: 2.2.0p23
Since Checkmk 2.2.0 there is a agent CA located in <code>etc/ssl/agents/</code>. This CA is
different from the site CA. In particular, if updating from 2.1.0 to 2.2.0,
Checkmk will create a symlink <code>etc/ssl/agents/legacy_ca.pem</code>, which points to
<code>etc/ssl/ca.pem</code>. After performing an <code>omd cp</code>. This symlink would still point
to the site, which was the source of the copy. The symlink is now relative. If
the site was created with version 2.2.0 or above no symlink is needed.
Title: netapp_ontap_info: enhanced presentation of NetApp system information
Class: fix
Compatible: compat
Component: checks
Date: 1707991443
Edition: cre
Level: 1
Version: 2.2.0p23
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 16493 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: netapp_ontap_snapvault: improves lagtime calculation
Class: fix
Compatible: compat
Component: checks
Date: 1708076378
Edition: cre
Level: 1
Version: 2.2.0p23
------------------------------------<diff>-------------------------------------------
Title: netapp_ontap_snapvault: improves lagtime calculation
Class: fix
Compatible: compat
Component: checks
Date: 1708076378
Edition: cre
Level: 1
Version: 2.2.0p23
- With this new type of calculation, since we don't have a reference for when this lagtime started or ended,
- we always consider a month to be made up of 30 days.
Title: netapp_ontap_snapvault: improves lagtime calculation
Class: fix
Compatible: compat
Component: checks
Date: 1708076378
Edition: cre
Level: 1
Version: 2.2.0p23
With this new type of calculation, since we don't have a reference for when this lagtime started or ended,
we always consider a month to be made up of 30 days.
Title: aws: Inventorization of EC2 and ELB tags as host labels
Class: fix
Compatible: compat
Component: checks
Date: 1708516567
Edition: cre
Level: 1
Version: 2.2.0p23
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)
# sla: range field for predefined_time_range parameter is mandatory
key | value
---------- | ---
date | 2024-02-23T08:00:57+00:00
version | 2.4.0b1
class | fix
edition | cee
component | rest-api
level | 1
compatible | yes
Before this werk, when the sla was computed for a predefined time
range without specifying the range field, an error status 500
Internal Server Error was returned. This werk solves the problem
by checking for the existence of the range field, and if it does
not exist, the endpoint returns an error status 400 - Bad Request.