[//]: # (werk v2)
# Let cmcdump handle semicolons in plugin output
key | value
---------- | ---
date | 2024-02-21T13:39:02+00:00
version | 2.4.0b1
class | fix
edition | cee
component | multisite
level | 1
compatible | yes
cmcdump would not handle semicolons correctly, leading to
garbled or incomplete output and spurious errors.
This has been fixed by escaping semicolons in cmcdump
and unescaping them in livestatus.
[//]: # (werk v2)
# mtr: Fix section parsing error
key | value
---------- | ---
date | 2024-02-25T22:30:51+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
When the mtr section contained a line that started with `**ERROR**`, the parsing of the section failed.
This has now been fixed.
The lines starting with `**ERROR**` will be ignored.
[//]: # (werk v2)
# Introduced topology visualization
key | value
---------- | ---
date | 2024-02-25T15:22:55+00:00
version | 2.4.0b1
class | feature
edition | cee
component | multisite
level | 2
compatible | yes
The topology visualization is a new feature that allows the visualization of complex interconnected networks.
A simple example for this visualization is the parent/child topology. The new mechanism that comes with this werk allows the linking of external data with the data of the monitoring core.
When it comes to the display, you simply define some starting points via the filter form.
Based on these, the topology visualization then builds a mesh of incoming and outgoing connections.
The type of external data might be
* Netstat, showing connections between the interfaces/ips/ports
* LLDP/CDP, showing the network neighbors
There is a common data format specification for all external data.
So you just can create your own data file which provides information about the relationships between hosts, services or generic objects which are not linked to the core.
If you drop this file into a specific folder, the visualization will handle the rest. There is no need to write python code.
Right now you can configure
* Objects - either linked to an entity in the core or some standalone object
* Icons/emblems which should be added to the object
* Connections between objects
* Line style/color of specific connections
Since this is a quite visualization heavy topic and hard to explain only via text, feel free to check out the
[thread](https://forum.checkmk.com/t/network-visualization-now-in-version-2-… in our checkmk forum
We will also publish a blog article in the coming weeks
```
Important:
The visualization only works if external data is provided in a special folder.
At the moment these are not created by Checkmk, but come from external MKP developments.
```
Title: EC: fix a wrong message on a matched rule
Class: fix
Compatible: compat
Component: ec
Date: 1708676070
Edition: cee
Level: 1
Version: 2.2.0p23
Previously, the tooltip on a matched rule would say it is a cancelling rule.
This message was misleading and was changed.
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.