ID: 13626
Title: Linux/Windows dashboards: Adjust titles for inv columns
Component: Multisite
Level: 1
Class: Bug fix
Version: 2.3.0b1
The column names have been too long in relation to the actual content in
the lines. Now the boards use shorter column names.
ID: 14798
Title: Extend discovery of cmciii waterflow sensors
Component: Checks & agents
Level: 1
Class: New feature
Version: 2.3.0b1
If you're using cmciii waterflow sensors which where not exactly named "Waterflow",
they haven't been discovered with Checkmk.
Now all sensors containing "Waterflow" in their name will be discovered.
ID: 14301
Title: Minor mail notification usability improvements
Component: Notifications
Level: 1
Class: Bug fix
Version: 2.3.0b1
Some minor usability improvements have been applied to the body of the mail
notifications.
The Host row now displays the alias only in case it is set and is different
from the hostname to reduce redundant information.
The "performance data" (aka metric) row is not displayed anymore by default
because it's considered a detail information that can be viewed in the UI if it
is needed. However, if you prefer to keep this in the notification, you can
configure this in the notification plugin settings.
ID: 15274
Title: brocade_fcport: wrong port speed
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
For certain configuration of Brocade FC Switches the "assumed speed"
(configurable, defaults to 2GByte/s) was displayed, although the
inventory table showed the correct port speed.
ID: 15172
Title: Interface checks: Fix rare interface mixups
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.3.0b1
In rare cases, the interface checks associated multiple interfaces with a given service item.
Depending on the exact plugin, this could lead to incorrect monitoring results (wrong data or
misleading failures in rate computations).
This happened if there was an interface where the combination of alias or description plus index
matched the alias or description (without the index) of another interface. For example, the
following combination lead to such as mixup:
LI: Item: `Ethernet 2`
LI: Interface 1: Index 1, Description `Ethernet 2`
LI: Interface 2: Index 2, Description `Ethernet`
In this case, Checkmk associated both interfaces with the item `Ethernet 2`, resulting in wrong
monitoring results.
Furthermore, another potential side effect of this issue was that the Perf-O-Meters of affected
services crashed with
C+:
Exception: list index out of range
C-:
ID: 14875
Title: shadow hosts custom attributes doesn't disappear anymore
Component: config
Level: 2
Class: Bug fix
Version: 2.1.0p15
Previously, shadow hosts custom attributes were ignored during
config generation.
With this release the problem has been eliminated.
ID: 15275
Title: apache_status.py: autodetection for processes with long pids
Component: agents
Level: 1
Class: Bug fix
Version: 2.3.0b1
In certain cases (processes with long pids) the autodetection of apache
instances did not work correctly.
The functionality was broken since Werk #14679 and should now be
fixed.
ID: 15179
Title: <tt>logwatch</tt> agent plugin: Always encode output in UTF-8
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
This werk is only incompatible if you monitor logfiles containing non-ASCII characters with the
<tt>logwatch</tt> agent plugin.
As of this werk, the <tt>logwatch</tt> agent plugin always encodes its ouput in UTF-8. Before, the
encoding depended on the system settings.
This werk is marked as incompatible because it can have an unexpected side effect: On some systems,
users might now have to explicitly configure the encoding of the monitored log files. The reason for
this is that if not explicitly configured, the <tt>logwatch</tt> plugin tries to guess the encoding.
If the wrong encoding is guessed, log files are decoded incorrectly, however, before this werk, this
error might have cancelled out due to <tt>logwatch</tt> using the same encoding both for decoding
logfiles and encoding its output.
Since the latter is now always done using UTF-8, this cancellation will not happen anymore. If you
are affected by this, you will either see the replacement character `�` appearing in your log
messages or your log messages will contain random non-ASCII characters which do not make sense.
As a positive side effect, correcting this issue enables the matching of patterns containing non-
ASCII characters. Before, using the wrong encoding to decode the logfiles prevented this,
effectively leading to overlooked messages.
ID: 15180
Title: <tt>logwatch</tt> agent plugin on Windows: Enable monitoring of log files with non-ASCII characters in their paths
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
Before this werk, the <tt>logwatch</tt> agent plugin crashed with
C+:
UnicodeEncodeError: 'ascii' codec can't encode character ...: ordinal not in range(128)
C-:
for log files whose paths contained non-ASCII characters.