We use cookies to ensure that we give you the best experience on our website.  Visit our Privacy Policy to learn more. If you continue to use this site, we will assume that you are okay with it.

Your choices regarding cookies on this site.
Your preferences have been updated.
In order for the changes to take effect completely please clear your browser cookies and cache. Then reload the page.

Werk #11142: PostgreSQL: Differentiate idle from active connections

ComponentChecks & Agents
TitlePostgreSQL: Differentiate idle from active connections
Date2020-07-13 16:40:08
Checkmk EditionCheckmk Raw Edition (CRE)
Checkmk Version2.0.0i1
LevelTrivial Change
ClassNew Feature
CompatibilityIncompatible - Manual interaction might be required

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.

Note: 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:

  • If you're monitoring both PostgreSQL and MongoDB: keep the old rule "Database Connections (PostgreSQL/MongoDB)" before updating to this werk.
  • If you're monitoring MongoDB only: delete the old rule "Database Connections (PostgreSQL/MongoDB)" before updating to this werk
  • Create a new rule with your previous settings for MongoDB with the new rule "Database Connections (MongoDB)"