Monitors and Alerts
Use Monitors to decide when problems become issues, and Alerts to notify, ticket, and automate next steps when those issues match your rules.
Sentry separates what you detect from what you do about it:
- Monitors watch your application's health and behavior. There are default detectors that pull data from your SDK integration. Custom configurations like cron schedules, HTTP uptime, and metric thresholds on errors, spans, logs, releases, and application metrics can also be monitored. With Monitors, these signals are turned into issues when conditions are met.
- Alerts run when issues match the triggers and filters you configure, and carry out actions like sending notifications via Slack, email, PagerDuty, or webhooks, or creating work items in Jira and similar tools.
Using both Monitors and Alerts gives you a path from signal → triageable issue → team workflow, without wiring every integration by hand for every edge case.
For a concise Issues-centric explanation (how this shows up in your triage flow), see Monitors and Alerts. For hands-on setup, see Creating an Alert.
flowchart LR
subgraph mon["Monitors"]
direction LR
M1[Listen for when to create issues]
end
subgraph iss["Issues"]
direction LR
I[Issue created or updated]
end
subgraph al["Alerts"]
direction LR
A[Triggers + filters + actions]
end
mon --> iss
iss --> al
- Monitor evaluates data on a schedule or on incoming events and decides whether to open or update an issue.
- Alert rules listen for issue lifecycle and attribute changes (and can be limited to certain Monitors or projects).
- When a rule matches, actions run: notify people, open tickets, call integrations.
| Goal | Documentation |
|---|---|
| Configure detectors (cron, uptime, metrics, defaults) | Monitors |
| Configure notifications, tickets, and webhooks | Alerts |
| Sentry notifications (email, quota, and so on) | Notifications |
| Reduce noise and choose thresholds | Alerts Best Practices |
Was this helpful?
Help improve this content
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").