add crons rate limit information to all platform pages (#10115)

getsentry · Jun 8, 2024 · 13f7906 · 13f7906
1 parent 1268314
commit 13f7906
Show file tree

Hide file tree

Showing 10 changed files with 23 additions and 0 deletions.
diff --git a/docs/platforms/dotnet/common/crons/index.mdx b/docs/platforms/dotnet/common/crons/index.mdx
@@ -33,3 +33,5 @@ Example: `The event's tags match monitor.slug equals my-monitor-slug-here`
 <Include name="common-imgs/crons-alerts-example" />
 
 Learn more in [Issue Alert Configuration](/product/alerts/create-alerts/issue-alert-config/).
+
+<Include name="crons-rate-limits" />
diff --git a/docs/platforms/elixir/crons/index.mdx b/docs/platforms/elixir/crons/index.mdx
@@ -27,3 +27,5 @@ Example: `The event's tags match monitor.slug equals my-monitor-slug-here`
 <Include name="common-imgs/crons-alerts-example" />
 
 Learn more in [Issue Alert Configuration](/product/alerts/create-alerts/issue-alert-config/).
+
+<Include name="crons-rate-limits" />
diff --git a/docs/platforms/go/common/crons/index.mdx b/docs/platforms/go/common/crons/index.mdx
@@ -33,3 +33,5 @@ Example: `The event's tags match monitor.slug equals my-monitor-slug-here`
 <Include name="common-imgs/crons-alerts-example" />
 
 Learn more in [Issue Alert Configuration](/product/alerts/create-alerts/issue-alert-config/).
+
+<Include name="crons-rate-limits" />
diff --git a/docs/platforms/java/common/crons/index.mdx b/docs/platforms/java/common/crons/index.mdx
@@ -27,3 +27,5 @@ Example: `The event's tags match monitor.slug equals my-monitor-slug-here`
 <Include name="common-imgs/crons-alerts-example" />
 
 Learn more in [Issue Alert Configuration](/product/alerts/create-alerts/issue-alert-config/).
+
+<Include name="crons-rate-limits" />
diff --git a/docs/platforms/javascript/common/crons/index.mdx b/docs/platforms/javascript/common/crons/index.mdx
@@ -280,3 +280,5 @@ Example: `The event's tags match monitor.slug equals my-monitor-slug-here`
 <Include name="common-imgs/crons-alerts-example" />
 
 Learn more in [Issue Alert Configuration](/product/alerts/create-alerts/issue-alert-config/).
+
+<Include name="crons-rate-limits" />
diff --git a/docs/platforms/php/common/crons/index.mdx b/docs/platforms/php/common/crons/index.mdx
@@ -27,3 +27,5 @@ Example: `The event's tags match monitor.slug equals my-monitor-slug-here`
 <Include name="common-imgs/crons-alerts-example" />
 
 Learn more in [Issue Alert Configuration](/product/alerts/create-alerts/issue-alert-config/).
+
+<Include name="crons-rate-limits" />
diff --git a/docs/platforms/python/crons/index.mdx b/docs/platforms/python/crons/index.mdx
@@ -92,3 +92,5 @@ Example: `The event's tags match monitor.slug equals my-monitor-slug-here`
 <Include name="common-imgs/crons-alerts-example" />
 
 Learn more in [Issue Alert Configuration](/product/alerts/create-alerts/issue-alert-config/).
+
+<Include name="crons-rate-limits" />
diff --git a/docs/platforms/ruby/common/crons/index.mdx b/docs/platforms/ruby/common/crons/index.mdx
@@ -27,3 +27,5 @@ Example: `The event's tags match monitor.slug equals my-monitor-slug-here`
 <Include name="common-imgs/crons-alerts-example" />
 
 Learn more in [Issue Alert Configuration](/product/alerts/create-alerts/issue-alert-config/).
+
+<Include name="crons-rate-limits" />
diff --git a/docs/product/crons/getting-started/http/index.mdx b/docs/product/crons/getting-started/http/index.mdx
@@ -251,3 +251,5 @@ Example: `The event's tags match monitor.slug equals my-monitor-slug-here`
 <Include name="common-imgs/crons-alerts-example" />
 
 Learn more in [Issue Alert Configuration](/product/alerts/create-alerts/issue-alert-config/).
+
+<Include name="crons-rate-limits" />
diff --git a/includes/crons-rate-limits.mdx b/includes/crons-rate-limits.mdx
@@ -0,0 +1,5 @@
+## Rate Limits
+
+Crons imposes a rate limit on check-ins to prevent abuse and resource overuse. Specifically, you can only send a maximum of **6 check-ins per minute per existing monitor environment**. This limit is enforced on a per-project basis, meaning that the rate limit applies collectively to all monitor environments within a given project. You can check if any of your check-ins are being dropped in the [Usage Stats](/product/stats/#usage-stats) page.
+
+To avoid dropped check-ins, it is crucial to manage and distribute your check-ins efficiently within the rate limits. This will help maintain accurate monitoring and ensure that all critical check-ins are captured and processed.