Services and Monitoring

Services & Monitoring

Monitored services with live status; the detail panel shows uptime (24h / 7d / 30d) and recent outages.

Track the services each host runs, watch them (and the hosts themselves) go up and down, and see uptime history.

Services registry

The Services tab lists services per host — name, host, port/protocol, status, optional URL and icon. Add them with + Service, or ⊕ Bulk to add several (e.g. a host's containers) at once. Tick rows → Delete selected to remove in bulk.

Each service links to a host, so Boltarr always knows which machine runs it.

Uptime monitor

Turn on monitoring for a service (its detail panel) and Boltarr probes it on a timer:

• URL present → HTTP(S) GET; any response = up. Connect error/timeout = down.
• Host + port → a TCP connection test.

Results:

• A live up/down dot in the services table (flips on the first failed check).
• Uptime % for the last 24h / 7d / 30d + a list of recent outages, in the detail panel. History is kept ~31 days and pruned automatically.
• Alerts (via Notifications): a down alert fires once a service has been continuously down past the grace period (alert after service down for), and a recovery alert when it comes back. Quiet hours are respected.

Host up/down & uptime (liveness)

A light background ping sweep (nmap -sn) marks every known host online/offline — the dot next to each IP. Configure it in Settings → 📡 Liveness (sweep interval, offline-after threshold).

• A host goes offline after a few consecutive missed sweeps, back online on the first response (brief blips don't false-alarm).
• Transitions record a change event and — for static hosts, unless opted out — fire an immediate, quiet-hours-aware alert.
• Host uptime: a host's Edit → Info → Liveness section shows its up/down + 24h/7d/30d uptime % + outages, just like services.

Host ↔ service correlation

Because services know their host, Boltarr connects the dots:

• Each service row shows its host's up/down.
• A down service whose host is offline gets a "host offline" tag — instant root cause ("why are 8 services down? → the server's down.").
• Alert suppression: when a host goes offline, its services' individual down-alerts are held, so you get one host-offline alert instead of a flood. Toggle in Settings → 📱 Notifications (on by default).

Public status page

Mark services (and hosts) public to show them on an external status page — see Public Status Page.