[checkmk-commits] [tribe29/checkmk] c9df43: cleanups for mssql_counters migration

Branch: refs/heads/master Home: https://github.com/tribe29/checkmk Commit: c9df431ce75cab878e5d25ed8df3e38bb81fe1d3 https://github.com/tribe29/checkmk/commit/c9df431ce75cab878e5d25ed8df3e38bb… Author: Moritz Kiemer &lt;moritz.kiemer(a)tribe29.com&gt; Date: 2020-08-13 (Thu, 13 Aug 2020) Changed paths: R checkman/mssql_counters M checks/mssql_counters Log Message: ----------- cleanups for mssql_counters migration Change-Id: I50b848523b258d0c966d6d4c3a49365dbcd0e8d6 Commit: d90a67368d6276e4dee124ce596e7a134e8fd6a3 https://github.com/tribe29/checkmk/commit/d90a67368d6276e4dee124ce596e7a134… Author: Lars Michelsen &lt;lm(a)tribe29.com&gt; Date: 2020-08-13 (Thu, 13 Aug 2020) Changed paths: A .werks/11261 M cmk/ec/main.py Log Message: ----------- 11261 FIX Fix performance regression caused by too many live status queries between EC and core The version 1.6.0p14 introduced an issue affecting the Event Console and it's Livestatus communication with the local monitoring core. Instead of querying static configuration related information, which is needed by the Event Console only once per core restart, these information were not cached as intended. This resulted in these queries being made over and over again. The query was executed in the following situations: <ul> <li>Multiple times when querying the "eventconsolestatus" table (Once for each host known by the Event Console)</li> <li>Once for each created event</li> </ul> Change-Id: Ibcfad43bfdce4745e9215bd3417b622a74a845a1 Commit: 7dfd67377fffc79f0eae0c4966911fff2e4ff68d https://github.com/tribe29/checkmk/commit/7dfd67377fffc79f0eae0c4966911fff2… Author: Lars Michelsen &lt;lm(a)tribe29.com&gt; Date: 2020-08-13 (Thu, 13 Aug 2020) Changed paths: A tests/unit/cmk/ec/test_host_config.py Log Message: ----------- Add test to verify caching of HostConfig Change-Id: I926952ed3cdb5dd145d3eba19054138539b49ea3 Compare: https://github.com/tribe29/checkmk/compare/15a0d0276b3d...7dfd67377fff