Problem Statement
We need a way to get alerted when the overall organization usage suddenly spikes, not just when a single project crosses a quota threshold.
Sentry already has a mechanism through billing notifications, which fire on fixed percentage-of-quota-consumed thresholds (80%/100%). This is a lagging signal tied to billing consumption rather than true anomaly detection. Genuine anomaly-detection and percent-change metric alerts exist in Sentry today, but are scoped to a single project, with no mechanism to apply that detection logic across aggregated, multi-project, or org-wide volume.
A volume spike in a single service can currently go undetected at the organization level until it registers against a billing threshold, by which point quota has often already been consumed.
Solution Brainstorm
- Support for detecting unexpected spikes in aggregate volume across all projects in an organization, not just a single project. This doesn't need to be limited to Sentry's existing "Anomaly Detection" alert type specifically — percent-change thresholds, static thresholds, or other spike-detection methods evaluated at the org level would also address this.
- Where possible, reuse existing detection approaches (e.g., dynamic/learned thresholds) but applied at the org level rather than per-project.
- Alert latency fast enough to surface spikes same-day, rather than after a multi-day delay.
Product Area
Other
Problem Statement
We need a way to get alerted when the overall organization usage suddenly spikes, not just when a single project crosses a quota threshold.
Sentry already has a mechanism through billing notifications, which fire on fixed percentage-of-quota-consumed thresholds (80%/100%). This is a lagging signal tied to billing consumption rather than true anomaly detection. Genuine anomaly-detection and percent-change metric alerts exist in Sentry today, but are scoped to a single project, with no mechanism to apply that detection logic across aggregated, multi-project, or org-wide volume.
A volume spike in a single service can currently go undetected at the organization level until it registers against a billing threshold, by which point quota has often already been consumed.
Solution Brainstorm
Product Area
Other