Sheet REL-02 · Endpoint Management Manual
Monitoring, Discovery & Automation
Alert rules, incidents, workflows, patch rollout, network discovery and the infrastructure map.
Alerts and incidents
- Create metric and event alert rules, snooze alerts and work the alert queue.
- Work incidents with their linked alerts and timeline.
- Dependency-aware suppression holds back non-critical alerts from downstream endpoints while an upstream endpoint has an active critical or high alert. Critical alerts always fire.
- Routing rules send notifications to the right channel, for example after-hours escalation.
Workflows, jobs and scripts
Workflows are versioned. You build steps, publish, then run them by hand or from a trigger. Before running a workflow on production endpoints you can:
- Dry-run it in simulation.
- Add approval steps.
- Roll it out to a canary group first.
Failed runs can be retried, and workflows have timeouts. The automation kill switch pauses all automated action at once.
Patching
Patch policies and ring sets control rollout. Each ring has a canary count and a cool-off period. A ring can require that a patch succeeded in the previous ring first. Deployments run inside maintenance windows and can be rolled back. Relay also tracks reboot compliance and patch KPIs.
Discovery and the infrastructure map
Discovery scans run from a probe: a managed endpoint on the network segment you want to scan. Discovered devices move through lifecycle states and can be promoted to managed endpoints.
The infrastructure map shows dependencies between endpoints and services. You can add manual edges and create service groups from the map. The same data drives the environment health view and the wallboard.