It’s primarily based on the number of log records, not total log byte volume. For Prefect Cloud in 3.x: - Logs + Events limits are rate limits by count per minute - Log size matters only for per-request/per-message caps, not as an account consumption metric So in practice: - If you emit 1,000 logs, that counts as 1,000 records - A larger log line does not consume more of your account’s log rate limit than a smaller one - But oversized payloads can still be rejected Relevant limits: - Account rate limits: logs/events per minute by plan - Request body max: about 5 MiB per API request; larger bulk log writes can fail with

413 Content Too Large

- Per-log max size: capped as well (default cloud max is around 25,000 characters per log message) If you want, I can also pull the current per-plan log/event limits and share them here.