Alert Recipients settings manage the people or mailboxes that can receive Mini DBA alert notifications. Recipients can then be organized into recipient groups for easier routing.
Availability helps determine whether a recipient should currently receive alerts. Use it for on-call rotations, temporary absences, or recipients that should remain configured but not actively notified.
Alert recipients should represent real operational ownership. Add recipients who can investigate or route database alerts, and avoid sending production alerts to unattended mailboxes unless they are part of a ticketing or audit workflow. For shared teams, use Recipient Groups so routing can be changed without editing every alert rule.
Review recipients regularly. People leave teams, mailboxes are retired, and on-call responsibilities change. Stale recipients create confusion during incidents and can expose operational details to the wrong audience. If a recipient should temporarily stop receiving alerts, change availability instead of deleting the record when you expect to use it again.
For urgent alerts, combine recipients with escalation tools such as PagerDuty Integration, Slack, Teams, or Jira depending on your incident process.
Use whichever matches your process. Shared mailboxes are useful for team visibility, while individuals work better for named ownership.
Availability helps decide whether a configured recipient should actively receive alert notifications.
Groups make routing easier to maintain when teams, customers, or server ownership change.