Operations

The notification carries the same explanation.

Every alert reaches your team through the channel they already watch — and it arrives with the same root-cause explanation you'd see in the dashboard, not a bare "something's wrong" ping that sends someone straight to a browser tab.

← Back to platform overview

5channel types built in

3ways to route: severity, asset, integration

1notification per incident, not per alert

Channels

Alerts where your team already is.

Slack

Microsoft Teams

PagerDuty

Opsgenie

Generic Webhook

Email & SMS

Why the Incident, Not the Alert

One notification, not three pages for one problem.

Because causal correlation collapses a cascade into a single incident before it ever reaches a notification channel, your team gets paged once — for the root cause — with the effect chain attached as context, instead of three separate, seemingly unrelated pings that all need to be manually connected back together at 3am.

🔧 Slack · #incidents

Root cause identified — mysql_too_many_connections on server-13, cascading to phpfpm_request_terminated_slow and nginx_502_bad_gateway.

Fix: increase max_connections or resolve the connection leak.

Routing

Route by what actually matters to you.

Route by	Example
Severity	Critical incidents to PagerDuty, warnings to a Slack channel
Asset	Production database alerts to the DBA team's channel, staging to a muted one
Integration	Security findings to a dedicated security-alerts webhook, everything else to Teams

Where We Stand

Scope, honestly.

What's covered

Slack, Teams, PagerDuty, Opsgenie, generic webhook, email, and SMS
Routing by severity, by asset, and by integration
Every notification carries the same root-cause explanation as the dashboard
One notification per correlated incident, not one per raw alert

What it isn't

Not a full incident-management platform with its own on-call scheduling — it routes into the tools that already do that (PagerDuty, Opsgenie) rather than replacing them
No built-in alert-fatigue analytics dashboard yet — routing rules are configured directly, not tuned by a separate insights layer

Pairs Well With

Related capabilities

Get In Touch

Reach us directly.

Offices in India and the US — reach out and we'll get back to you.