Alerts, Notifications, and Incidents

Three different signals

Rivolq separates alerts, notifications, and incidents on purpose.

They are related, but they are not the same thing.

What an alert is

An alert is a system-detected operational signal that should lead to action.

Examples:

• a critical asset is entering a risky state
• an important PM is overdue
• a work backlog pattern is getting worse
• a support or platform condition needs responder attention

Alerts should be actionable and tied to an owner.

What a notification is

A notification is the delivery layer.

It tells a user something happened, but it does not automatically mean the condition is urgent.

Notifications can cover:

• alert delivery
• workflow updates
• support messages
• billing or admin events
• account and security events

What an incident is

An incident is a coordinated-response event with real business, customer, safety, or compliance impact.

Not every alert is an incident. Incidents require:

• clear ownership
• escalation
• communication
• a more deliberate response path

Practical rule of thumb

Use this mental model:

1. 01alert = operational condition
2. 02notification = how the system tells someone
3. 03incident = coordinated response when the impact is larger

If your team starts ignoring alerts

Review:

• whether thresholds are too noisy
• whether the alerts are routed to the right people
• whether the action path is obvious
• whether repeated notifications are hiding the real signal

The goal is attention that leads to work, not wallpaper.