ID: 12558
Title: Fix "Remote alert handlers (Linux)" rule processing
Component: Setup
Level: 1
Class: Bug fix
Version: 2.1.0i1
Checkmk 2.0 was not able to display values of rules created with previous
Checkmk versions. The rules created with Checkmk 2.0 were also not displayed
correctly and additionally were not processed correctly during agent baking.
Rules created with previous 2.0 releases need to be deleted and recreated.
ID: 12740
Title: Fix unique naming of host and service labels
Component: Multisite
Level: 1
Class: Bug fix
Version: 2.1.0i1
Sorters und columns of view used the title "Labels" for host and service
labels.
ID: 12682
Title: f5_bigip_mem: item disappears from monitoring data
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.1.0i1
Since Check_mk version 2.0.0, the F5 BIGIP memory services show an UNKNOWN
status with the message "item not found in monitoring data". This has been
fixed.
ID: 12736
Title: Honor date and timestamp format parameter in automation calls of views
Component: Multisite
Level: 1
Class: Bug fix
Version: 2.1.0i1
The parameter "po_ts_date" and "po_ts_format" were ignored on automation calls.
If you've used this parameter for automation calls before, please check to see
if adjustments are required.
ID: 12485
Title: Apply limits in Alert Statistics views
Component: Multisite
Level: 1
Class: Bug fix
Version: 2.1.0i1
Alert Statistics views and reports had an unconstrained query limit to
accurately calculate results. Yet after resulting rows have been aggregated
it is still desirable to present only a limited amount of results.
This Werk enforces the Alert Statistics views to only display results
within the query limits.
ID: 12681
Title: f5_bigip_fans: could not detect speed when speed is equal to 0
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.1.0i1
The f5_bigip_fan check returned the status message "could not detect speed" in
the event that speed was 0 RPM. This has been fixed.
ID: 12649
Title: Fix for Crash "Unhandled exception: TypeError('can only concatenate str (not "bytes") to str')"
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.1.0i1
The active check "check_mail" crashed if the payload was encoded with base64. This werk fixes this issue.
ID: 12194
Title: dell_compellent_folder: Fix discovery error when data missing
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.1.0i1
Discovery of dell_compellent_folder failed when data was missing.
Service with missing data is no longer discovered.
ID: 12169
Title: Fixed potential deadlock when archiving event console events
Component: Event Console
Level: 2
Class: Bug fix
Version: 2.1.0i1
When lots of event console events are being archived while lots of new
events are created, there was the possibility of a deadlock between the EC
and the CMC. This has been fixed.
ID: 12728
Title: <tt>cisco_asa_failover</tt>: Improve monitoring of Cisco ASA Failover
Component: Checks & agents
Level: 1
Class: New feature
Version: 2.1.0i1
This werk improves the monitoring of Cisco ASA Failover setups (check
plugin <tt>cisco_asa_failover</tt>).
<ul>
<li>The corresponding service is now also discovered on Cisco
Firepower devices.</li>
<li>The service is renamed from "Cluster Status" to "Failover Status".
Already existing services will continue to work, however, new services
will be detected under the new name. This renaming is necessary because
ASA clusters are something completely different than ASA failover pairs.
In ASA clusters, up to 16 identical devices are connected by a control
link and they all handle traffic at the same time. Cisco ASA failover
pairs on the other hand consist of two identical devices connected by a
failover link. Only one of the these devices, the active one, handles
traffic. The other one is in standby and only takes over in case the
active unit fails.</li>
<li>The check plugin now has two additional configuration options
(ruleset "Failover states"): the monitoring status in case either the
local or the remote device are not active or in standby and the
monitoring status in case the failover link is not up. Previously,
these monitoring statuses we hard-coded to WARN and CRIT, which is still
the default.</li>
</ul>