PostgresqlNotEnoughConnections fires as a false positive on small deployments

[dstathis]

The alert fires constantly on a lightly-loaded deployment even though PostgreSQL is healthy and the application is working correctly.

Steps to reproduce

1. Deploy postgresql-k8s and relate to cos (or cos-lite)
2. Relate postgresql-k8s to a consumer charm and don't use it very much (I am using joplin-server)
3. Check the firing alerts

Expected behaviour

No alerts when the deployment is healthy

Actual behaviour

Continuous alerts

Versions

Operating system: Nixos 25.11

Juju CLI: 3.6.20-genericlinux-amd64

Juju agent: 3.6.14

Charm revision: 774

microk8s: -
k3s: v1.34.5+k3s1

Log output

Juju debug log:

Additional context

[syncronize-issues-to-jira]

Thank you for reporting your feedback to us!

The internal ticket has been created: https://warthogs.atlassian.net/browse/DPE-9730.

This message was autogenerated

[dstathis]

Upon further inspection this alert is labeled as "severity: info". My config was suppressing warning but not info level alerts. So perhaps this is in fact fine.

[taurus-forever]

Hi, I believe today it works accordingly to the spec:
https://warthogs.atlassian.net/browse/DPE-3161

The awesome alert rule 2.2.7: PostgreSQL instance should have more connections (> 5).
Should it be just above 0? @7annaba3l