Sentry sends notifications to keep you informed about errors, performance regressions, and quota usage. You can control which events trigger notifications, how they’re delivered, and tune the settings per project.
Notification types
Issue alerts
Workflow
Deploy
Quota
Weekly reports
Spike protection
Issue alert notifications fire when an alert rule you’ve configured is triggered. Rules evaluate conditions like “a new issue is created” or “an issue is seen more than N times in an hour.” Each project can have multiple alert rules, and each rule can notify different people or channels.By default, you receive notifications for all issues in projects you are a member of. You can change this to subscribe-only (you must manually subscribe to an issue) or turn issue alerts off entirely.
Workflow notifications keep you updated on activity for issues you’re involved with. They fire when:
- An issue you are subscribed to changes status (resolved, regressed, ignored)
- A comment is posted on an issue you follow
- You are assigned to an issue
- You are mentioned in a comment
The default setting is subscribe only, meaning you receive these notifications only for issues you are actively subscribed to. Deploy notifications tell you when a release is deployed to an environment. The default setting is committed only, meaning you only receive deploy notifications for releases that include commits authored by you. You can switch this to always (every deploy) or never.
Quota notifications alert you when your organization approaches or reaches usage limits. Separate toggles exist for each data category:
- Errors
- Transactions / spans
- Replays
- Attachments
- Cron monitor seats
- Profile duration
- Uptime monitors
You also receive a warning notification when you reach 80% of a reserved quota, and a second notification at 100%. These are on by default and can be turned off individually. The weekly email digest summarizes new issues and trends across your projects for the past week. It’s sent every Monday and is on by default. You can disable it in your personal notification settings.
Spike protection notifications fire when Sentry detects an unusual surge in event volume and automatically drops excess events to protect your quota. You’ll be notified when spike protection activates and when it deactivates.
Personal notification settings
Your personal settings control defaults across all organizations and projects you belong to.
Open your notification settings
Go to User Settings > Notifications.
Adjust each category
For each notification type, choose your preferred frequency:| Option | Behavior |
|---|
| Always | Receive notifications for all matching events |
| Subscribe only | Receive notifications only for issues you’ve subscribed to (workflow only) |
| Committed only | Receive notifications only when you authored a commit in the release (deploy only) |
| Never | Disable this notification type |
Choose delivery channels
Select how you want each notification type delivered: email, Slack (if your organization has the Slack integration installed), or both.
If your organization has the Sentry mobile app and you’ve logged in, you can also receive push notifications for issue alerts on your phone.
Per-project overrides
You can override your global notification settings for individual projects. This is useful if you want more coverage on a critical production project and less noise from a low-priority one.
- Go to User Settings > Notifications.
- Scroll to the Project Alerts section.
- Use the dropdowns next to each project to set a project-specific preference.
Project-level overrides take precedence over your global defaults for that project only.
Notification delivery channels
| Channel | Requirement |
|---|
| Email | Always available |
| Slack | Slack integration must be installed at the organization level |
| Mobile push | Must be logged into the Sentry mobile app |
You can configure Slack to send issue alert notifications to specific channels or DMs through Settings > Integrations > Slack at the organization or project level.
Reducing notification noise
If you’re receiving too many notifications, try these approaches:
Snooze an issue — Open the issue and click Snooze. Sentry will stop sending notifications for it until it reoccurs or a set time passes.
Adjust alert rule thresholds — In Settings > [Project] > Alerts, edit existing alert rules to raise the threshold (for example, require 10 occurrences instead of 1 before alerting).
Change workflow setting to subscribe-only — In User Settings > Notifications, set Workflow to Subscribe only. You’ll only get notified about issues you explicitly subscribe to.
Unsubscribe from specific issues — On any issue detail page, click the bell icon to toggle your subscription. 
