Notifications

Notifications (ntfy)

Boltarr sends alerts to your phone via ntfy — a simple pub/sub push service (use the public server or self-host).

Setup

Settings → 📱 Notifications:

1. Enabled — turn it on.
2. Server — https://ntfy.sh or your self-hosted URL.
3. Topic — a unique, hard-to-guess topic name (anyone who knows it can read your alerts on the public server).
4. Access token — only if your ntfy server requires a login.
5. Send test — confirm it works.

Then subscribe to your topic in the ntfy mobile/desktop app to receive alerts.

Global alert behavior

Also under Notifications:

• Alert after service down for — grace period before a service-down alert fires (0 = immediate). Avoids alerting on brief blips.
• Suppress service-down alerts when the host is offline (on by default) — if a host goes down, you get one host-offline alert instead of a flood of alerts for every service on it. See Services and Monitoring.
• Quiet hours — mute alerts during a window (your local Configuration). Anything still down when the window ends alerts you then; overnight change findings roll into the morning digest. Scans and monitoring still run during quiet hours — only the alerts are held.

What can notify you

• Service monitor — down + recovery (Services and Monitoring).
• Change alerts — new hosts, port/MAC/hostname changes, host offline/online, as per-scan summaries and/or a daily digest (Change Tracking and Alerts).
• Host liveness — a static host going offline/online (immediate).

Not getting alerts? Check Enabled + topic subscribed, quiet hours, and the change-alert scope (static/dynamic/all). See Troubleshooting.