Skip to content

Raise the OTLP request limit to 512 MiB - #126

Closed
haggs wants to merge 2 commits into
mainfrom
dhaggerty/ase-1316-langsmith-export-still-drops-signal-spans-on-large-compass-128mib
Closed

haggs wants to merge 2 commits into
mainfrom
dhaggerty/ase-1316-langsmith-export-still-drops-signal-spans-on-large-compass-128mib

Conversation

@haggs

@haggs haggs commented Nov 3, 2026 •

Copy link
Copy Markdown
Contributor
  • Raise the OTLP exporter request limit from its 64 MiB default to 512 MiB.
  • Keep the existing batching and delivery behavior to test whether the higher limit alone preserves large runs.

Verified locally: stopped the latest 512 MiB run during insight compilation after all four signal spans and all 92 candidate validations ended. The endpoint returned 11 HTTP 413 responses; the largest attempted batch was 372.09 MiB. There were no client size-limit drops or DNS errors in this attempt. Raising the client limit alone leaves a receiving-side size rejection; the enforcing component and exact limit are still unknown. The earlier completed 128 MiB experiment stored 2,208 of 2,678 observed spans.

@haggs haggs changed the title Raise the OTLP request limit to 128 MiB Raise the OTLP request limit to 512 MiB Nov 3, 2026
@haggs haggs closed this Nov 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant