Slack & webhook alerts

Pages with the answer in the message, not a link to a dashboard.

"5xx alarm fired" is not a page — it's a guessing game. Radar's pages include the failing service, the dominant error, the correlated deploy, the customer-impact verdict, and a confidence score. Open Slack, read one message, decide.

What you'll actually see
#infra-alerts · radar14:22 UTC
R
RadarAPP · agentincident · INC-2041
🛰 Signal detected · payments-api

p99 latency rose to 11.4s (baseline 2.1s) shortly after deploy v3.42.1. Cascading 5xx on users-api via job-events queue (depth ×4.2).

customer-facingdeploy-correlatedconfidence · high
threaded

14:25 · auto-rollback completed. Watching for recurrence over next 30m.

14:55 · No recurrence. Marking resolved.

What changes for the on-call engineer

Read once, act once

The headline tells you the verdict. The body tells you why. The thread tracks the resolution.

Threaded follow-ups

Related blips and the resolution itself land in the same thread — your channel stays clean.

Slack, webhooks, PagerDuty

Same payload, multiple destinations. Route critical pages to your on-call rotation.

How it works

step · 01

Connect a channel

Add Slack with one OAuth click, or paste a generic webhook URL.

step · 02

Pick services

Subscribe each channel to specific services or tiers from the service map.

step · 03

Tune

Mute confidence < medium, or noise-suppress a known recurring finding from the alert itself.

Resolve incidents in 30 seconds, not 30 minutes.

Connect your AWS account in read-only mode and let Radar take the next page.