PagerDuty settings connect Mini DBA alerting to a PagerDuty service. Use this integration for incidents that require on-call escalation.
PagerDuty should be reserved for alerts that need someone to take action, especially outside normal working hours. Route high-severity database availability, backup, storage, and production performance alerts to PagerDuty, but keep informational or noisy alerts in email, Slack, Teams, reports, or the Mini DBA console.
Use a dedicated PagerDuty service for database monitoring when possible. This keeps escalation policies, ownership, and incident history clear. For managed service providers, use customer or environment context in alert names and recipient groups so the on-call engineer can identify the affected estate quickly.
Test the integration after saving the key and after any PagerDuty service changes. If incidents do not appear, check the integration key, network/proxy access, alert severity routing, and Service Log.
No. Only actionable alerts should page someone. Excessive paging creates alert fatigue.
Check the integration key, service status, proxy settings, Mini DBA service logs, and whether the alert is routed to PagerDuty.
Yes. Use PagerDuty for urgent escalation and other channels for visibility, summaries, or lower-severity alerts.