Skip to content

chore(billing): Remove grace period mentions #15685

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mrduncan wants to merge 2 commits into
base: master
Choose a base branch
from
Open

chore(billing): Remove grace period mentions #15685

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
242213e
chore(billing): Remove grace period mentions
mrduncan Dec 1, 2025
12bf09d
Merge branch 'master' into mrduncan/remove-grace-period
jaffrepaul Dec 2, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 0 additions & 6 deletions docs/pricing/quotas/manage-event-stream-guide.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -51,12 +51,6 @@ Once the changes are applied, sort the "Results" table by the "COUNT()" column t

Once you know where your quota is being used, you can start taking the steps below to control it.

## Grace Period

All accounts have access to a one-time grace period. This means that if an account depletes its error event volume and has never previously triggered a grace period, we continue to accept events for the next three days at a maximum rate of 10,000 events per hour. If you choose not to increase your error volume, Sentry will stop accepting events for the remainder of the current billing month. However, if you increase your volume, error events accepted during the grace period will be counted as consumed volume.

While this grace period isn't dependent on the [Spike Protection feature](#7-spike-protection), you'll probably get a notification that you've entered a grace period along with a notification of a spike.

## Spike Protection

Spike Protection protects users from spiking event volume. Typically, spikes are caused by anomalies and have the potential to deplete your available event volume rapidly. Your baseline consumption is used to compute a threshold and spike protection is triggered if event volume exceeds this threshold. When spike protection is triggered, events start getting dropped, ensuring that you don't get charged for the excess volume.
Expand Down
Loading