From bd9100d02296ffedfffa905d381b37584eeeb4af Mon Sep 17 00:00:00 2001 From: Colton Padden Date: Sat, 14 Dec 2024 19:04:20 -0500 Subject: [PATCH 1/2] [docs-beta] migrate - rate limits doc --- .../dagster-plus/deployment/management/rate-limits.md | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/docs/docs-beta/docs/dagster-plus/deployment/management/rate-limits.md b/docs/docs-beta/docs/dagster-plus/deployment/management/rate-limits.md index b4364e74ff276..87889d3db6d76 100644 --- a/docs/docs-beta/docs/dagster-plus/deployment/management/rate-limits.md +++ b/docs/docs-beta/docs/dagster-plus/deployment/management/rate-limits.md @@ -1,6 +1,12 @@ --- title: Dagster+ rate limits -unlisted: true --- -{/* TODO move from https://docs.dagster.io/dagster-plus/references/limits */} \ No newline at end of file +Dagster+ enforces several rate limits to smoothly distribute the load. Deployments are limited to: + +- 40,000 user log events (e.g, `context.log.info`) per minute. This limit only applies to custom logs; system events like the ones that drive orchestration or materialize assets are not subject to this limit. +- 35MB of events per minute. This limit applies to both custom events and system events. + +Rate-limited requests return a "429 - Too Many Requests" response. Dagster+ agents automatically retry these requests. + +Switching from [Structured event logs](/concepts/logging#structured-event-logs) to [Raw compute logs](/concepts/logging#raw-compute-logs) or reducing your custom log volume can help you stay within these limits. From b2ee19456c4ee4c473bb02db4c87d8599a9fbfb0 Mon Sep 17 00:00:00 2001 From: Colton Padden Date: Thu, 19 Dec 2024 13:28:32 -0500 Subject: [PATCH 2/2] todo links --- .../docs/dagster-plus/deployment/management/rate-limits.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/docs-beta/docs/dagster-plus/deployment/management/rate-limits.md b/docs/docs-beta/docs/dagster-plus/deployment/management/rate-limits.md index 87889d3db6d76..7c85eb8fdaa11 100644 --- a/docs/docs-beta/docs/dagster-plus/deployment/management/rate-limits.md +++ b/docs/docs-beta/docs/dagster-plus/deployment/management/rate-limits.md @@ -9,4 +9,5 @@ Dagster+ enforces several rate limits to smoothly distribute the load. Deploymen Rate-limited requests return a "429 - Too Many Requests" response. Dagster+ agents automatically retry these requests. -Switching from [Structured event logs](/concepts/logging#structured-event-logs) to [Raw compute logs](/concepts/logging#raw-compute-logs) or reducing your custom log volume can help you stay within these limits. +{/* Switching from [Structured event logs](/concepts/logging#structured-event-logs) to [Raw compute logs](/concepts/logging#raw-compute-logs) or reducing your custom log volume can help you stay within these limits. */} +Switching from [Structured event logs](/todo) to [Raw compute logs](/todo) or reducing your custom log volume can help you stay within these limits.