Problem Statement
When we run a planned audit that causes a big but expected spike in errors, Sentry’s spike protection turns on (as expected) but then keeps triggering afterward during normal traffic.
This causes:
- Extra “spike protection triggered/ended” emails
- Some real production events being dropped even when volume looks normal
Can spike protection handle planned spikes (like audits or load tests) better so that:
- A one-time, intentional spike doesn’t make the system overly sensitive afterward
- We don’t lose normal production events or get noisy alerts once traffic is back to usual
Product Area
Settings - Spike Protection
Problem Statement
When we run a planned audit that causes a big but expected spike in errors, Sentry’s spike protection turns on (as expected) but then keeps triggering afterward during normal traffic.
This causes:
Can spike protection handle planned spikes (like audits or load tests) better so that:
Product Area
Settings - Spike Protection