PgbouncerErrors

PgbouncerErrors #

PGBouncer is logging errors. This may be due to a a server restart or an admin typing commands at the pgbouncer console.

Alert Rule
alert: PgbouncerErrors
annotations:
  description: |-
    PGBouncer is logging errors. This may be due to a a server restart or an admin typing commands at the pgbouncer console.
      VALUE = {{ $value }}
      LABELS = {{ $labels }}    
  runbook: https://srerun.github.io/prometheus-alerts/runbooks/spreaker-pgbouncer-exporter/pgbouncererrors/
  summary: PGBouncer errors (instance {{ $labels.instance }})
expr: increase(pgbouncer_errors_count{errmsg!="server conn crashed?"}[1m]) > 10
for: 0m
labels:
  severity: warning

Here is a runbook for the PgbouncerErrors alert rule:

Meaning #

The PgbouncerErrors alert is triggered when the number of errors logged by Pgbouncer increases by more than 10 in a 1-minute period, excluding errors with the message “server conn crashed?”.

Impact #

This alert indicates that Pgbouncer is experiencing errors, which may be caused by a server restart or an administrator interacting with the Pgbouncer console. If left unchecked, these errors could lead to connectivity issues or data loss.

Diagnosis #

To diagnose the issue, follow these steps:

  1. Check the Pgbouncer logs for error messages to identify the root cause of the errors.
  2. Verify that no recent server restarts or maintenance activities have occurred.
  3. Investigate if any administrative commands were executed on the Pgbouncer console.
  4. Review the Pgbouncer configuration to ensure it is correct and up-to-date.

Mitigation #

To mitigate the issue, follow these steps:

  1. Investigate and resolve the underlying cause of the errors, based on the diagnosis.
  2. Restart the Pgbouncer service to clear any transient errors.
  3. Verify that the Pgbouncer configuration is correct and up-to-date.
  4. Monitor the Pgbouncer logs for any further errors.

Additional resources:

Edit this page