Slack Alerts
Get notified on Slack when something breaks in production.
Connect DeepTracer to Slack so your team gets notified the moment something goes wrong. No more checking dashboards — alerts come to you.
What triggers alerts
DeepTracer sends Slack alerts for three types of events:
- AI investigation results — when DeepTracer finishes investigating an error, you get a summary with the root cause and suggested fix.
- Threshold rule triggers — when an error rate, response time, or other metric crosses a threshold you've set.
- Uptime down events — when a monitored endpoint goes down.
Each alert includes an error summary and a direct link to your DeepTracer dashboard for the full details.
Setup
Create a Slack webhook
Go to the Slack Incoming Webhooks page and create a new webhook for the channel where you want alerts.
- Create a new Slack app (or use an existing one)
- Enable Incoming Webhooks
- Click Add New Webhook to Workspace
- Pick the channel and authorize
- Copy the webhook URL — it looks like
https://hooks.slack.com/services/T.../B.../xxx
Add the channel in DeepTracer
In your DeepTracer dashboard, go to Settings > Alert Channels and click Add Channel.
- Select Slack as the channel type
- Paste your webhook URL
- Give it a name (e.g. "prod-alerts" or "#engineering")
- Choose which environments should trigger alerts (e.g. only production)
- Choose which severity levels to include
- Save
Send a test alert
After saving, click Send Test next to your new channel. You should see a test message appear in Slack within a few seconds. If it doesn't arrive, double-check your webhook URL.
Alert message format
Each Slack message includes:
- Error type and message
- Project and environment
- Occurrence count and affected users
- AI-generated summary (when an investigation is available)
- Direct link to the error in your DeepTracer dashboard
Muting alerts
During a deployment or planned maintenance, you can temporarily pause alerts to avoid noise. In Settings > Alert Channels, click the mute toggle next to any channel. Un-mute when you're done.
Muting pauses notifications only — DeepTracer still monitors and records everything. You won't miss data, just the Slack messages.
Tips
- One channel per environment — create separate channels like
#prod-alertsand#staging-alertsso production noise doesn't drown out staging issues (or vice versa). - Filter severity — set up a high-severity channel that only fires for critical errors, and a separate one for warnings.
- Use threads — Slack threads keep related alerts together. DeepTracer groups follow-up messages about the same error into threads automatically.
What's next?
- Alerts — Learn about threshold rules and alert configuration
- AI Investigations — How DeepTracer analyzes your errors
- Uptime Monitoring — Monitor your endpoints