fix(config): Increase default max_span_size from 1 MiB to 10 MiB#5780
Merged
vgrozdanic merged 2 commits intomasterfrom Apr 8, 2026
Merged
fix(config): Increase default max_span_size from 1 MiB to 10 MiB#5780vgrozdanic merged 2 commits intomasterfrom
vgrozdanic merged 2 commits intomasterfrom
Conversation
The previous 1 MiB default was too restrictive for spans in the spans_v2 pipeline, causing legitimate large spans to be rejected with HTTP 413. Co-Authored-By: Claude <noreply@anthropic.com>
loewenheim
approved these changes
Apr 7, 2026
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Increases the default
max_span_sizein relay config from 1 MiB to 10 MiB.With the new DACI new limit per span is 1MB (this will be changed in sentry codebase to still come as a config), but that means that we now need to raise
max_span_sizeto higher value.max_span_sizeis used to check if the span will even get to trimming or will immediately get rejected, so if we left it at 1 MiB we'd never trim any larger span the limit, which is not the behavior that we want.The change is done here, in the code, and not through config to address also the managed relays which do not read our k8s configs.