Alerts and root cause
When the database goes down, the team needs one signal about the database, not twenty about the services that depend on it.
The task
A failure of a core service causes failures in every dependent one. The person on call gets dozens of notifications and spends time figuring out what really happened.
How it is solved
Dependencies between resources describe what depends on what. Alerts of dependent resources are linked to the root cause and do not duplicate notifications, but stay in the feed. An alert can be acknowledged, snoozed or turned into an incident.
What is included
- Severity levels: info, warning, major, critical
- Acknowledging alerts one at a time or in bulk
- Snoozing without escalation for a while
- Suppressing dependent alerts by root cause
- Alert event history
- Creating an incident from an alert with fields filled in
Limitations
- The root cause is determined from the resource dependencies you described.
What depends on the plan
This feature is available in every plan and has no separate limit.
Compare plansQuestions about this feature
Will alerts from dependent services disappear?
No. They are visible in the feed and linked to the root cause, but do not send separate notifications.
How do I avoid alerts during maintenance?
Schedule maintenance with alerts muted for the affected resources.
Where it helps
Other features
All featuresCheck your services today
The free plan includes checks, a status page and a team of up to three people. The setup wizard takes you from a product to the first notification.