NiteWtch - Sensor alert to voice escalation flow
Animated flow showing a NiteWtch sensor pulling config, collecting checks, posting metrics, creating alerts, escalating by voice, and closing by acknowledgment.
NiteWtch - Sensor alert to voice escalation flow
Sensor agent -> config pull -> local checks -> metrics ingest -> alert decision -> escalation -> voice acknowledgment
Color key
Processing / movement
Durable or gated state
Accepted / success path
Escalation / retry path
Sensor Agent
host watcher
Remote Config
pull + hot reload
Local Checks
cpu disk http service
Metrics Ingest
queue + POST
Alert Engine
threshold + liveness
Backend Alert
dedupe + suppress
Escalation
voice call
Voice Ack
digit closes loop
Sensor agent watches the host from the inside
A lightweight enrolled agent collects health signals and checks in with the regional API.
Enroll
runtime secret
Pull Config
no inbound port
Collect
host + network
Heartbeat
liveness
Remote config controls what the sensor checks
Admins change checks in NiteWtch; the sensor picks up revisions on its next poll.
Admin Policy
check rules
Revision
versioned
Poll API
200 / 304
Hot Reload
apply safely
Collectors turn host behavior into checks
The agent samples local resources and synthetic checks on the configured interval.
Resources
cpu mem disk
Network
ping tcp http
Services
running state
Result
normalized
Metrics ingest keeps charts useful and resilient
Check results are validated, posted to the regional API, and queued locally if the network is down.
Validate
contract
Disk Queue
retry later
POST Metrics
regional API
Store
charts/history
Alert engine catches breaches and missing check-ins
Local thresholds and backend liveness both create sensor-origin alerts when needed.
Thresholds
local eval
Breach
alert event
Liveness
missed check-ins
Recovery
resolved state
Backend alert processing is shared across intake paths
Sensor alerts enter the same incident, suppression, routing, and escalation pipeline.
Normalize
sensor source
Suppression
maint + dedupe
Alert Row
always log
Voice Gate
critical + active
Escalation places one voice call at a time
Routing resolves primary/failover groups, then tracks call attempts and outcomes.
Resolve
primary/failover
Pick Target
next user
Call Attempt
INITIATED
Voice API
voice callout
Voice outcome decides the next step
Answered calls can acknowledge; missed or wrong responses continue escalation.
Decision
answer + digit?
Ack?
correct digit
Next User
no ack
Failover
secondary group