Operations

Investigating an alert without duplicate noise

Use event history and preferences to move from a notification to a decision.

Start with the affected asset

Confirm the active workspace, alert timestamp, source check and recent status changes. A notification may be deduplicated while the underlying event remains in history.

Follow-up

  1. Review the latest completed check and its evidence.
  2. Compare with the previous known-good period.
  3. Check whether another operator has already acknowledged or investigated it.
  4. Use the enabled notification preferences to choose the right recipient for future events.

Never infer that a suppressed duplicate alert means the condition was fixed.

Before taking action

Confirm the active workspace, required permission, registered asset, and freshness of the data being used.

← Back to documentation