Branch: refs/heads/master Home: https://github.com/tribe29/checkmk Commit: bf6a5c2cc72fbc578a3f35d27d22234ead9e9e41 https://github.com/tribe29/checkmk/commit/bf6a5c2cc72fbc578a3f35d27d22234ea… Author: Timotheus Bachinger &lt;timotheus.bachinger(a)tribe29.com&gt; Date: 2020-07-17 (Fri, 17 Jul 2020) Changed paths: A tests/unit/checks/generictests/datasets/postgres_connection_old.py Log Message: ----------- Add regression test for old postgres output Change-Id: Ie9b70ed46552fedc5bd0a7f9384a8f0bf78b82f9 Commit: 8e740c05d64cc9073552d0ee15cdf9082d086524 https://github.com/tribe29/checkmk/commit/8e740c05d64cc9073552d0ee15cdf9082… Author: Timotheus Bachinger &lt;timotheus.bachinger(a)tribe29.com&gt; Date: 2020-07-17 (Fri, 17 Jul 2020) Changed paths: A .werks/11142 M agents/plugins/mk_postgres M agents/plugins/mk_postgres.py M checkman/postgres_connections M checks/mongodb_connections M checks/postgres_connections M cmk/gui/plugins/metrics/network.py M cmk/gui/plugins/metrics/perfometers.py M cmk/gui/plugins/wato/check_parameters/db_connections.py A tests/unit/checks/generictests/datasets/postgres_active_idle.py M tests/unit/checks/generictests/datasets/postgres_connection_old.py Log Message: ----------- 11142 PostgreSQL: Differentiate idle from active connections Previously, the agent plugin "mk_postgres" and the check plugin "postgres_connections" were not differentiating between "idle" and "active" connections. With this werk, the data to differentiate those states is obtained and evaluated accordingly. The WATO rule "Database Connections (PostgreSQL)" (renamed from "Database Connections (PostgreSQL/MongoDB)") has now a dedicated option for setting the levels for "active" and "idle" connections. In case the rule was used previously, the default connection type for PostgreSQL will be "active" as the old agent was excluding "idle" connections. <b>Note:</b> As this WATO rule was applicable as well for MongoDB, this change will be incompatible to previously existing MongoDB rules set with "Database Connections (PostgreSQL/MongoDB)". If this is applicable for your setup, perform the following steps: <li> If you're monitoring both PostgreSQL <b>and</b> MongoDB: keep the old rule "Database Connections (PostgreSQL/MongoDB)" before updating to this werk.</li> <li> If you're monitoring MongoDB <b>only</b>: delete the old rule "Database Connections (PostgreSQL/MongoDB)" before updating to this werk</li> <li> Create a new rule with your previous settings for MongoDB with the new rule "Database Connections (MongoDB)" </li> Change-Id: Id2233a4f9b7df18978f8f3d6bebda76a8a3e5ae4 Commit: e463d2509eec7bc545b064fb46df9014a63daa52 https://github.com/tribe29/checkmk/commit/e463d2509eec7bc545b064fb46df9014a… Author: Sven Panne &lt;sven.panne(a)tribe29.com&gt; Date: 2020-07-17 (Fri, 17 Jul 2020) Changed paths: M livestatus/src/Table.cc Log Message: ----------- YAPF'd. Change-Id: If35dbb1590b1eb5b9cc01c031d44e51e5282f9e8 Compare: https://github.com/tribe29/checkmk/compare/939ed0d4aa28...e463d2509eec