Sentry Alerts have been split into two features. Now you can leverage context, assignment and triage across all of your Sentry data, as well as exercise more control over what you want to monitor, and how your team gets notified.
- Monitors detect problems and create issues. Define what to track across your data - when a threshold is breached, Sentry creates an issue automatically.
- Alerts are triggered by issues and handle notification routing. Define who gets paged, when, and how. One alert can connect to many monitors, so you configure routing once and reuse it everywhere.
What does this mean for my old alerts?
- If you had Metric Alerts: Issue detection thresholds have been migrated automatically to Metric Monitors. Check your Monitors tab to see them. Alerting Actions have been migrated to Alerts - you can find them in Connected Alerts.
- If you want to update notification routing: Go to Alerts in the left nav.
- If you used Cron or Uptime: Those are now in the Monitors tab too.
We now have 5 different Monitor type:
- Metric: query span attributes, logs, application metrics, error counts, crash rates, and application performance. Set fixed, or relative thresholds; or detect anomalies in seasonal data dynamically.
- Cron: track the health of any scheduled, recurring job. Get an issue created when a job misses its check-in window, runs too long, or fails.
- Uptime: monitor any HTTP endpoint for availability and reliability. Get an issue created when your endpoint goes down, becomes unresponsive or responds in an unexpected way.
- Mobile Builds: track mobile build size and catch regressions before they ship.
- Error: managed by Sentry automatically. Flags incoming error codes and creates issues based on your project's error grouping rules.
How do I create a Metric Monitor?
Navigate to Monitors in the left nav, click Create Monitor, then select Metric as your monitor type.
Step 1. Choose your project and environment
Select the project and environment where issues will be created.
Step 2. Choose your metric
Select from a list of pre-configured metric types like number of errors, crash rate, or span duration.
Step 3. Customize your metric
Customize your data further by defining the interval, visualization, and adding any additional filters required.
Step 4. Issue detection
Choose how Sentry detects a problem and creates an issue:
- Threshold — triggers when a fixed value is crossed, best for non-seasonal data
- Change — triggers on percentage changes over a defined time window
- Dynamic — auto-detects anomalies, best for seasonal or noisy data
Set your high and medium priority thresholds to define when an issue is created, escalated, resolved, and re-opened.
Step 5. Issue ownership
Assign issues created by this monitor to an individual or team. Use the description field to add debugging steps or context for your teammates.
Step 6. Preview
Review a sample of the issues this monitor configuration would produce before saving.
Step 7. Connect an alert
Connect an existing alert or create a new one to define who gets notified when this monitor creates an issue.
Click Save Monitor.
How do I create an Alert?
Navigate to Alerts in the left nav and click Create Alert . If creating an Alert from the Monitors creation flow, click “+ Create New Alert” and skip to step 3.
Step 1: Source
Chose your project.
- All issues in a project — alert fires on any issue created in the project
- Issues from specific monitors — alert fires only on issues created by monitors you select
Step 2. Filter issues
Narrow down which environments this alert applies to.
Step 3. Alert builder
Define your alert logic using WHEN / IF / THEN conditions:
- WHEN — choose the trigger event (new issue created, issue resolved, issue escalates, resolved issue becomes unresolved)
- IF — add filters to narrow which issues trigger the alert
- THEN — select the action (Slack, email, PagerDuty, and more)
Add multiple IF/THEN blocks to route different issue types to different channels.
Use Send Test Notification to confirm your routing is working.
Step 4. Throttle
Set how often this alert can fire for a given issue to reduce noise.
Click Create Alert.
Check out our Monitors & Alerts docs.
FAQ
Q: I can't find my old alerts. Where did they go?
A: Your existing alert rules migrated automatically to Monitors. Head to the Monitors tab in the left nav to find them. If you're looking for notification routing specifically, that lives under Alerts.
Q: Why am I getting more notifications than before?
A: When a monitor threshold is breached, Sentry creates an issue — which may trigger both your existing issue alerts and your migrated alert rules. If you're seeing more noise than expected, you can filter out metric monitor issues using if/then conditions in your alert routing rules (for example: "issue type is not equal to metric monitor"). Learn how to manage alert noise.
Q: What's the difference between a Monitor and an Alert now?
A: A Monitor defines what to track and when to create an issue. An Alert defines who gets notified when that issue is created. One alert can connect to many monitors — so you set up your notification routing once and it applies everywhere you need it.
Q: Do I need to recreate anything?
A: No. Existing metric alert rules migrated automatically. If you used Crons or Uptime, those moved to the Monitors tab. If you notice anything missing or behaving unexpectedly please reach out to Support.
Q: How do I manage Monitors with Terraform?
A: A beta release of Sentry’s Terraform Provider is currently available with support for new sentry_alert and sentry_metric_monitor resources (among other new monitor resources).
Q: Where did the Insights tab go?
A: The Insights tab has been removed. Here's where everything went:
- Crons and Uptime → Monitors tab
- Performance views (frontend, backend, mobile, AI, and Sentry MCP) → Dashboards
Q: What are Mobile Build Monitors?
A: Mobile Build Monitors are integrated with our Size Analysis feature and let you create issue when certain build constraints are violated. You can read more about it here.