Branch: refs/heads/master Home: https://github.com/tribe29/checkmk Commit: a16bd0a2e7c4fb72b7a53a4f4e081f2cc23586c9 https://github.com/tribe29/checkmk/commit/a16bd0a2e7c4fb72b7a53a4f4e081f2cc… Author: thl-cmk &lt;thl-cmk(a)outlook.com&gt; Date: 2021-04-12 (Mon, 12 Apr 2021) Changed paths: A .werks/12728 M checkman/cisco_asa_failover M cmk/base/config.py M cmk/base/plugins/agent_based/cisco_asa_failover.py M cmk/gui/plugins/wato/check_parameters/cisco_asa_failover.py M tests/unit/cmk/base/plugins/agent_based/test_cisco_asa_failover.py Log Message: ----------- 12728 <tt>cisco_asa_failover</tt>: Improve monitoring of Cisco ASA Failover 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> Closes #357 Change-Id: Ie65720e01ec812fd481458c21fef58ec3d8081fc Commit: 77a530635353cc19a97f6066cdc883efa8118ebd https://github.com/tribe29/checkmk/commit/77a530635353cc19a97f6066cdc883efa… Author: Sven Panne &lt;sven.panne(a)tribe29.com&gt; Date: 2021-04-12 (Mon, 12 Apr 2021) Changed paths: A .werks/12169 Log Message: ----------- 12169 FIX Fixed potential deadlock when archiving event console events 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. Change-Id: I8d95a6ce69191a66865b7c7e9bba0d3cd8d82edd Compare: https://github.com/tribe29/checkmk/compare/13aa6fb42629...77a530635353