From 539d594103cc4558660b9e7f0ed2efe3b02ada77 Mon Sep 17 00:00:00 2001 From: isabellaenriquez Date: Wed, 30 Apr 2025 09:58:44 -0700 Subject: [PATCH 1/3] fix(spike protection): correct floor calculation explanation --- docs/pricing/quotas/spike-protection.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/pricing/quotas/spike-protection.mdx b/docs/pricing/quotas/spike-protection.mdx index 73f6441e806d8..a70c8dea028d4 100644 --- a/docs/pricing/quotas/spike-protection.mdx +++ b/docs/pricing/quotas/spike-protection.mdx @@ -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 our paid plans 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. ### Usage-Based Calculation From 921a5378321e4f47ef2f6f859a2d9263dad47db3 Mon Sep 17 00:00:00 2001 From: isabellaenriquez Date: Wed, 30 Apr 2025 10:02:38 -0700 Subject: [PATCH 2/3] it's actually free plan --- docs/pricing/quotas/spike-protection.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/pricing/quotas/spike-protection.mdx b/docs/pricing/quotas/spike-protection.mdx index a70c8dea028d4..3bec91c436db5 100644 --- a/docs/pricing/quotas/spike-protection.mdx +++ b/docs/pricing/quotas/spike-protection.mdx @@ -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 1/10th of the minimum reserved volume quota on our paid plans 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. ### Usage-Based Calculation From fdaf8e80e33665722a130aa55e81733042b1f655 Mon Sep 17 00:00:00 2001 From: isabellaenriquez Date: Thu, 1 May 2025 11:29:10 -0700 Subject: [PATCH 3/3] colon --- docs/pricing/quotas/spike-protection.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/pricing/quotas/spike-protection.mdx b/docs/pricing/quotas/spike-protection.mdx index 3bec91c436db5..7c68a3e195631 100644 --- a/docs/pricing/quotas/spike-protection.mdx +++ b/docs/pricing/quotas/spike-protection.mdx @@ -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 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. ### Usage-Based Calculation