PostgreSQL alerts

PostgreSQL Alerts shows alerts for one monitored PostgreSQL server. Use it to focus alert triage on that instance.

> Community Edition: If this PostgreSQL server is monitored by a Community Edition engine, selecting Alerts shows an explanation instead of this alert-management page. Connect it through a trial or licensed engine to enable alert evaluation, history, configuration, and notifications. Licensed-engine servers remain fully enabled in mixed-engine Consoles. See Alert availability.

Workflow

1. Open Alerts under the PostgreSQL server.
2. Review severity, time, and message.
3. Open the related PostgreSQL page for investigation.
4. Use Configure and Copy Config to edit or copy alert policy.
5. Use global Alerts for estate-wide alert review.

How to use PostgreSQL alerts

PostgreSQL Alerts is a focused view for one monitored PostgreSQL instance. Use it when you already know which server is affected and want to avoid the noise of estate-wide alert lists. The page is useful during incidents, daily checks, and follow-up reviews after a PostgreSQL performance or availability problem.

Start with alerts that are high severity, new, repeating, or close to the time users reported a problem. Then open the related PostgreSQL page to validate the evidence. For example, an activity or blocking alert should be checked against PostgreSQL Activity, while configuration and maintenance warnings may need PostgreSQL Health Checks or PostgreSQL Server Log.

Alerts should create a clear next action. Record whether the alert was acknowledged, escalated, fixed, or accepted as a known condition. For managed service reporting, use alert history alongside Reports and Enterprise View.

Use Copy, Export, And Import Alert Configuration when this PostgreSQL server should inherit a standard PostgreSQL alert profile from another server, another connected engine, or an exported trigger file.

PostgreSQL alert FAQ

Why do I also see alerts on the global alerts page?

This page is server-specific. The global Alerts page is better for cross-engine triage and estate-wide prioritization.

What if an alert does not match a visible problem?

Check the alert time window, thresholds, and collection status. Some alerts indicate early warning conditions rather than current user impact.

Should every PostgreSQL alert be escalated?

No. Escalate by severity, business impact, recurrence, and whether the condition is new or already accepted.

Alert type reference

The following Mini DBA PostgreSQL alert detail pages explain why each alert is useful, when to enable it, how to tune thresholds, and what remediation steps to take when the alert is active. Custom Alert is included because each server Alerts page can also hold user-defined query alerts.

Related pages

• Alerts
• Copy, Export, And Import Alert Configuration
• PostgreSQL activity
• PostgreSQL health checks