Alerts

Alerts are conditions that need attention. They can come from a deterministic rule threshold or an SPC control.

Open Monitor → Alerts to search and filter the alert list. Open Details to see the evidence and manage the response.

What an alert includes

• Severity, creation time, and description.
• Current status and assignee.
• The rule threshold or SPC control that fired.
• The triggering event when one exists.
• Instrument, method, run, and file context when available.
• Notification state, investigation notes, and status history.

Triage workflow

1. Review the trigger and follow the linked event or run to its evidence.
2. Set the alert to Acknowledged when someone has started investigating.
3. Assign an owner.
4. Add notes to the alert history as you learn more or hand work to another person.
5. Use Snoozed for a known condition that should be quiet until a specific date and time. Record the reason.
6. Set the alert to Resolved when the response is complete.

A resolved alert can be set back to Open if the condition returns or the investigation needs to continue.

Muting versus snoozing

Snoozing changes one alert's response state. Muting suppresses new notifications from the configuration that produced the alert for a selected period; the underlying activity remains recorded. Use muting carefully so an active issue does not become invisible to the team.

See Alerting conditions for rule-based triggers and Statistical process control for statistical triggers.