fix(spike protection): correct floor calculation explanation #13556
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
2 Skipped Deployments
|
Bundle ReportChanges will decrease total bundle size by 15 bytes (-0.0%) ⬇️. This is within the configured threshold ✅ Detailed changes
Affected Assets, Files, and Routes:view changes for bundle: sentry-docs-client-array-pushAssets Changed:
view changes for bundle: sentry-docs-server-cjsAssets Changed:
|
vbro
approved these changes
Apr 30, 2025
|
@vbro nope i just came up with that stylization hence why i would like to wait on docs team for any language nits |
coolguyzone
reviewed
May 1, 2025
| @@ -81,7 +81,7 @@ As mentioned above, our Spike Protection Algorithm is based on the higher of two | |||
|
|
|||
| ### Minimum Event Calculation | |||
|
|
|||
| This calculation, which is the first step of our algorithm, identifies a minimum number of events, using your quota as a guide. This number takes the maximum of either 500 events or the result of the following formula `(3 \* your quota)/(720 \* number of projects)`. The number of projects is capped at 5 and is used to adjust the floor. The equation represents your project using up three times your overall quota in 30 days if events are continually ingested at this hourly rate, thus flagging the project for a potential spike. | |||
| This calculation, which is the first step of our algorithm, identifies a minimum number of events, using your quota as a guide. This number takes the maximum of either 1/10th of the minimum reserved volume quota on the Developer plan for that event type or the result of the following formula `(3 \* your quota)/(720 \* number of projects)`. The number of projects is capped at 5 and is used to adjust the floor. The equation represents your project using up three times your overall quota in 30 days if events are continually ingested at this hourly rate, thus flagging the project for a potential spike. | |||
There was a problem hiding this comment.
Suggested change
| This calculation, which is the first step of our algorithm, identifies a minimum number of events, using your quota as a guide. This number takes the maximum of either 1/10th of the minimum reserved volume quota on the Developer plan for that event type or the result of the following formula `(3 \* your quota)/(720 \* number of projects)`. The number of projects is capped at 5 and is used to adjust the floor. The equation represents your project using up three times your overall quota in 30 days if events are continually ingested at this hourly rate, thus flagging the project for a potential spike. | |
| This calculation, which is the first step of our algorithm, identifies a minimum number of events, using your quota as a guide. This number takes the maximum of either 1/10th of the minimum reserved volume quota on the Developer plan for that event type or the result of the following formula: `(3 \* your quota)/(720 \* number of projects)`. The number of projects is capped at 5 and is used to adjust the floor. The equation represents your project using up three times your overall quota in 30 days if events are continually ingested at this hourly rate, thus flagging the project for a potential spike. |
coolguyzone
approved these changes
May 1, 2025
codyde
added a commit
that referenced
this pull request
May 5, 2025
* 'master' of https://github.com/getsentry/sentry-docs: Fix small typo (#13570) Update trace explorer doc for GA (#13560) feat(cloudflare): Add jsonc instructions for sourcemaps upload (#13572) fix(apple): Missing semicolons in objc config snippets (#13578) feat(godot): Enriching events with scene tree data (#13531) feat(apple): Troubleshooting for subclass error (#13509) Make the API Design doc a bit more consistent (#13511) docs(js): Remove outdated/misleading warning (#13484) Refine SDK behavior docs for logs to make buffering more clear (#13573) fix(spike protection): correct floor calculation explanation (#13556) ref(docs): rm session health from early adopter (#13571) Bump API schema to 8c0365cd (#13564) Updating MCP docs with Video + Claude steps (#13563)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
DESCRIBE YOUR PR
The Minimum Event Calculation section hasn't been updated to account for the different minimum floors for each SKU.
500is only relevant to errors.IS YOUR CHANGE URGENT?
Help us prioritize incoming PRs by letting us know when the change needs to go live.
SLA
Thanks in advance for your help!
PRE-MERGE CHECKLIST
Make sure you've checked the following before merging your changes: