Request a demo

Guide · Incident management

Incident management: root incident, affected incident, and alarm noise

How a signal turns into an incident, why the root/affected distinction is critical, and practices that reduce alert fatigue.

From signal to incident

A failed check on its own is just a signal. A signal can be transient, can disappear, can be forgotten. An incident, on the other hand, is a trackable record: it carries a start time, affected resource, monitoring type, severity, and review and resolution status.

Root incident and affected incident

When a switch goes down, every dependent check fails at the same time. Looking at this cluster without separating it out pushes the operator to start from a random alarm.

The root incident marks the most likely starting point of the cluster; the other records are grouped as affected incidents. This is a priority indicator, not a declaration of definitive root cause.

Reducing alert fatigue

Notification noise is a configuration problem, not a tool problem. The following practices noticeably reduce noise.

  • Separate severity levels according to genuinely different business impacts.
  • Use root/affected grouping; do not send a separate notification for every record.
  • Split notification channels by responsible team.
  • Review the threshold and retry settings of checks that produce false positives.
  • Record operator feedback on resolved incidents.

Related terms

FAQ

Are affected incidents closed automatically?

No. They are grouped separately but not closed; seeing the affected scope is necessary for informing business units.

Demo request

Get in touch

Tell us about your environment and the targets you want to monitor; let's work out the right setup method and pricing together.

A monitoring plan that fits your needs

  1. 01Number of targets to monitor
  2. 02Check types and frequency
  3. 03Usage needs

Email: sales@mintyfi.com

Leave your details

We use cookies for visit statistics. Cookie policy