Signal Clusters

A Cluster groups the related raw events that survive noise suppression into one candidate Signal. It gives operators one place to assess impact, ownership, timing, and whether the problem should become an Incident.

​

Cluster lifecycle

A single-signal Cluster can route straight from Forming, without waiting for correlation. A critical-severity signal takes this path. Resolving an Incident does not close its Cluster. A later matching Signal opens a successor Incident, and the Cluster follows it. The Pulse lanes add an attention view on top of this lifecycle. Needs you shows unacknowledged high or critical forming Clusters without an owner. All shows Clusters across every visible state.

​

Noise suppression

Before a Signal contributes to a Cluster, Pulse applies eight suppression layers: A Cluster Pulse judges non-actionable is also suppressed, and appears as Not Actionable in the suppression breakdown.

Suppression analysis helps identify which sources create the most avoidable noise.

​

Review a Cluster

Open a Cluster to inspect its event history, severity, source, timestamps, and routing state.

Cluster detail keeps the evidence for one operational problem together.

Use the available actions to move the work forward: When you snooze a Cluster, choose the duration. When the Signal names a specific resource, the snooze covers that resource; otherwise it covers the source and event-type pattern.

​

Related