DND OverrideStart with the monitoring app and Android
- Confirm the monitoring service sends push notifications for the incidents you need.
- Open the app's Android notification settings and inspect its categories.
- If “incidents,” “critical,” or a similar category exists, make it alerting and allow it in DND or Modes.
- Send a test alert with DND active.
A first-party on-call feature with escalation, acknowledgement, repeated alerts, phone calls or SMS is usually stronger than a generic notification utility. Prefer it when available.
Add a text rule only when needed
If urgent and routine updates share one app/category, create an app + keyword rule. Example text might include DOWN, CRITICAL, production and failed. Choose “all keywords” if two terms must both appear, or use one case-sensitive regex for a tightly defined pattern.
DND Override has no native integration with PagerDuty, Grafana, UptimeRobot, AWS, Datadog, Home Assistant or any other monitoring platform. It can only react to the Android notification posted by the platform's own app.
Overnight checklist
- Keep Android notification access enabled for DND Override.
- Make sure alarm volume is above zero.
- Exclude the app from aggressive manufacturer battery/background restrictions if listener delivery proves unreliable.
- Verify that the source notification contains the expected text.
- Test updates as well as brand-new incidents; changed content can produce a new alert.
- Maintain an independent escalation path for consequential incidents.
Not an on-call platform: DND Override does not acknowledge, retry, escalate or guarantee delivery. Use your monitoring provider's supported on-call mechanisms for business-critical response.
For rule syntax, see keyword notification alerts and notification rules on Android.