One inbox for every alert
Pipe events in from Sentry, CloudWatch, Datadog, Grafana, or any custom system. Routing rules turn raw events into incidents. Auto-deduped, severity-tagged, and paged.
One inbox, many sources
Stop juggling tabs. Sentry errors, CloudWatch alarms, Datadog monitors, custom webhooks. All in one queue.
Routing rules
Match on severity, project, tags. Send Sentry fatals to on-call, low-priority warnings to a Slack channel.
Auto-dedup
The same alert firing 100 times in a minute becomes one incident. No event-storm pages.
Native source adapters
Plug in your existing observability stack with minimal config. Each source gets a unique ingest URL and we know how to parse the payload.
- Sentry. Error events with project, level, environment, release, fingerprint
- AWS CloudWatch Alarms. Alarm state changes with threshold and dimensions
- Datadog. Monitor alerts with priority, tags, and host context
- Grafana. Alert rule firings with dashboard links
- Generic JSON. Bring your own payload format, we extract via JSONPath
- Available on Pro and Business plans
Event Sources · 4 active
Sentry · production
/events/se_abc123…
CloudWatch · billing
/events/cw_def456…
Datadog · APM
/events/dd_ghi789…
Routing rules with field matching
Not every event is a wake-someone-up event. Define rules to route by severity, project, tag. Fatal Sentry errors create P1 incidents and page on-call; warnings go to a Slack channel.
- Match on event fields. Level, project, tag, environment, custom JSON path
- Outcomes. Create incident (with severity), notify channel, suppress, or both
- Per-rule cooldown to prevent thrashing during bursts
- Test mode. Replay a payload and see which rule would fire
- Drag-to-reorder rules. First match wins
Routing rules · Sentry production
→ create incident · page on-call
→ create incident · notify #ops
→ notify #monitoring · no incident
Auto-deduplication
A single bug can fire the same Sentry error 10,000 times in 60 seconds. We collapse identical events into one incident automatically. Your on-call sees one page, not ten thousand.
- Configurable dedup window per source (default: 60 seconds)
- Identity is provider-aware. Sentry uses fingerprint, CloudWatch uses alarm ARN
- Incident counter shows total events folded under one parent
- Manually break the dedup if a similar-but-different event needs separate handling
Last 60 seconds
DedupedEvents in
10,234
Incident
1
Recent events log
When a routing rule misbehaves, you need to know why. Every source has a recent-events log so you can replay payloads, see which rule matched (or didn't), and debug without polling your team.
- Last 50 events per source with full JSON payload
- Match badge. Shows which rule (if any) processed each event
- Filter by matched / unmatched / suppressed
- Replay button. Re-process an event after fixing a rule
Recent events · Sentry
From event to incident
Sentry fires a fatal. We ingest it, match a rule, dedup against the last 60 seconds, create a P1 incident, group it with related alerts, and page on-call. In under a second.