DeepTracer
Features

Alerts

Get notified on Slack, email, or webhook when something breaks.

DeepTracer sends you alerts when your app needs attention — so you don't have to watch the dashboard all day. Get notified the moment an error spikes, an endpoint goes down, or an AI investigation finds something critical.

Alert channels

DeepTracer supports three ways to receive alerts:

ChannelBest for
SlackTeam notifications. Alerts go to a channel everyone can see.
EmailPersonal notifications. Good for solo devs or off-hours alerts.
WebhookCustom integrations. Send alert data to any URL (PagerDuty, Discord, etc.).

You can set up multiple channels — for example, Slack for your team and email for critical-only alerts.

What triggers alerts

DeepTracer sends alerts for:

  • AI investigation results — When an automatic investigation completes, the findings are sent to your channels
  • Error spikes — A sudden increase in error rate beyond normal levels
  • New critical errors — A never-before-seen error with critical severity
  • Threshold rules — Custom rules you define (e.g., "alert me if more than 50 errors per minute")
  • Uptime downs — When a monitored endpoint stops responding

Setting up alerts

Go to Settings

Open your project dashboard and navigate to Settings (gear icon in the sidebar).

Open Alert Channels

Click the Alert Channels tab.

Add a channel

Click Add Channel and choose Slack, email, or webhook. Follow the prompts to connect your account or enter the destination URL.

Filtering alerts

Not every alert matters equally. You can filter what each channel receives:

By environment

Only get alerts for specific environments. Most teams set up:

  • Slack channel — production alerts only
  • Email — production and staging

This way, your development errors don't clutter your alert feed.

By severity

Filter alerts by error severity:

  • Critical only — Only the most urgent issues
  • High and above — Critical + high severity
  • All — Every alert, including low severity

Muting alerts

Deploying a big update? Doing planned maintenance? You can mute any alert channel temporarily.

Muting is useful when:

  • You're deploying and expect a brief spike in errors
  • You're doing database migrations
  • You're actively debugging and don't need notifications

Muted channels stop receiving alerts, but DeepTracer still tracks everything. When you unmute, you won't get a backlog of missed alerts — check the dashboard for anything that happened while muted.

Slack integration

For Slack setup details, see the Slack integration guide.

What's next?

On this page