fix(spike protection): clarify cap on num_projects in heuristic (#8869)

getsentry · Jan 12, 2024 · 731524d · 731524d · vercel · Jan 12, 2024
1 parent b333996
commit 731524d
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/src/docs/product/accounts/quotas/spike-protection.mdx b/src/docs/product/accounts/quotas/spike-protection.mdx
@@ -82,7 +82,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 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 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.
 
 ### Usage-Based Calculation