Skip to main content
Pulse is the Detect stage of Resolve. It receives raw provider events, removes known noise, groups related survivors into Clusters, and classifies each Cluster into a Signal that can route into an Incident.

​
What Pulse does

Pulse creates the Incident before RCA begins. Turning On Duty (automatic investigation) off pauses automatic analysis; it does not stop detection or Incident creation.

​
Work from the queue

Pulse organizes Clusters into these lanes: Open a Cluster to inspect its Signals, source, severity, timing, and routing state. From the Cluster you can Acknowledge, Assign, Escalate, or Resolve.
Pulse workspace with correlated operational signals

Pulse keeps related operational signals together so you can review the problem as one unit.

​
Connect a source

Open Resolve → Integrations to connect a platform and configure how Resolve listens for Signals. A source is ready after at least one webhook, polling, or chat path succeeds.

Understand clusters

Follow the Cluster lifecycle and review suppression behavior.

Connect Pulse sources

Configure a platform to send or expose operational Signals.

Pulse Analytics

Measure correlation yield, suppression, volume, and Cluster MTTR.

Manage integrations

See each platform’s connections, signal paths, and outcomes.