From 13f7906eb81e42674d53d254013646cba71af4a6 Mon Sep 17 00:00:00 2001 From: Gabriel Lopes Date: Thu, 23 May 2024 11:20:20 -0700 Subject: [PATCH] add crons rate limit information to all platform pages (#10115) --- docs/platforms/dotnet/common/crons/index.mdx | 2 ++ docs/platforms/elixir/crons/index.mdx | 2 ++ docs/platforms/go/common/crons/index.mdx | 2 ++ docs/platforms/java/common/crons/index.mdx | 2 ++ docs/platforms/javascript/common/crons/index.mdx | 2 ++ docs/platforms/php/common/crons/index.mdx | 2 ++ docs/platforms/python/crons/index.mdx | 2 ++ docs/platforms/ruby/common/crons/index.mdx | 2 ++ docs/product/crons/getting-started/http/index.mdx | 2 ++ includes/crons-rate-limits.mdx | 5 +++++ 10 files changed, 23 insertions(+) create mode 100644 includes/crons-rate-limits.mdx diff --git a/docs/platforms/dotnet/common/crons/index.mdx b/docs/platforms/dotnet/common/crons/index.mdx index 5b5843a2e8883..f6298ca18aef2 100644 --- 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` Learn more in [Issue Alert Configuration](/product/alerts/create-alerts/issue-alert-config/). + + diff --git a/docs/platforms/elixir/crons/index.mdx b/docs/platforms/elixir/crons/index.mdx index 94c62a2e6630f..7fec7cf5762bf 100644 --- 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` Learn more in [Issue Alert Configuration](/product/alerts/create-alerts/issue-alert-config/). + + diff --git a/docs/platforms/go/common/crons/index.mdx b/docs/platforms/go/common/crons/index.mdx index c65e13ac41caf..03d4b256ec850 100644 --- 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` Learn more in [Issue Alert Configuration](/product/alerts/create-alerts/issue-alert-config/). + + diff --git a/docs/platforms/java/common/crons/index.mdx b/docs/platforms/java/common/crons/index.mdx index 379ff3aeb02a5..4dd1e04581150 100644 --- 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` Learn more in [Issue Alert Configuration](/product/alerts/create-alerts/issue-alert-config/). + + diff --git a/docs/platforms/javascript/common/crons/index.mdx b/docs/platforms/javascript/common/crons/index.mdx index 8b3604ad514fb..364c2e19d405b 100644 --- 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` Learn more in [Issue Alert Configuration](/product/alerts/create-alerts/issue-alert-config/). + + diff --git a/docs/platforms/php/common/crons/index.mdx b/docs/platforms/php/common/crons/index.mdx index 379ff3aeb02a5..4dd1e04581150 100644 --- 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` Learn more in [Issue Alert Configuration](/product/alerts/create-alerts/issue-alert-config/). + + diff --git a/docs/platforms/python/crons/index.mdx b/docs/platforms/python/crons/index.mdx index ae90b91b1fa70..2c28c65fa1b64 100644 --- 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` Learn more in [Issue Alert Configuration](/product/alerts/create-alerts/issue-alert-config/). + + diff --git a/docs/platforms/ruby/common/crons/index.mdx b/docs/platforms/ruby/common/crons/index.mdx index 379ff3aeb02a5..4dd1e04581150 100644 --- 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` Learn more in [Issue Alert Configuration](/product/alerts/create-alerts/issue-alert-config/). + + diff --git a/docs/product/crons/getting-started/http/index.mdx b/docs/product/crons/getting-started/http/index.mdx index 8184993e6a91a..2cb8b2b6b89ae 100644 --- 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` Learn more in [Issue Alert Configuration](/product/alerts/create-alerts/issue-alert-config/). + + diff --git a/includes/crons-rate-limits.mdx b/includes/crons-rate-limits.mdx new file mode 100644 index 0000000000000..ffcda7a4893d7 --- /dev/null +++ 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.