PostgreSQL server ping ms alert


The Server Ping Ms alert notifies you when its configured condition is met on PostgreSQL instances so you can investigate and respond.

Screenshot pending: Mini DBA PostgreSQL Server Ping Ms alert screenshot placeholder

Alert summary

  • Platform: PostgreSQL
  • Alert category: Availability
  • Default enabled: true
  • Default evaluation frequency: Minute
  • Threshold label: Milliseconds
  • Unit: Ms

What Mini DBA checks

Mini DBA describes this alert as: Time taken for server to respond to ping requests Mini DBA evaluates this alert once a minute so changes are detected quickly.

How this alert helps

This alert protects availability by warning when Mini DBA cannot reach the monitored PostgreSQL instance or when the service state changes unexpectedly. It is often the first signal that users will see connection failures before deeper diagnostic metrics can be collected.

When to enable it

Enable it on every production and customer-facing PostgreSQL instance. For development systems, keep it enabled only when the instance is expected to be continuously available or when it supports automated testing and demos.

Threshold guidance

Threshold meaning: Milliseconds. Major threshold: 5000 Ms. Minor threshold: 1000 Ms. Comparison direction: over. For an over-threshold alert, decreasing a threshold makes that severity fire sooner; increasing it tolerates more load or pressure. Set the minor threshold as an early-warning level and the major threshold at the highest acceptable value for the service.

Remediation for an active alert

Confirm the host, listener, service, firewall, DNS, and credentials first. Check whether planned maintenance is in progress, then use the relevant PostgreSQL activity and service logs to decide whether the problem is network, engine startup, authentication, or resource exhaustion.

Investigation workflow

  1. Confirm the alert is still active and note the first seen time, affected instance, and severity.
  2. Review the current metric, the recent trend, and the affected database, login, host, or application in Mini DBA before changing configuration or ending sessions.
  3. Compare the current value with the normal baseline for the same time of day or maintenance window.
  4. Record the cause, corrective action, and whether thresholds or routing should be adjusted after the incident.

Avoiding alert noise

If the alert creates repeated noise, review whether it is enabled on the correct instances, whether maintenance windows are configured, and whether the minor and major routes match the real business impact. Keep enough history to prove the new setting before changing it broadly.

Related pages