Batch metrics submission to avoid HTTP 413 on large builds#385
Open
yoannmoinet wants to merge 1 commit into
Open
Batch metrics submission to avoid HTTP 413 on large builds#385yoannmoinet wants to merge 1 commit into
yoannmoinet wants to merge 1 commit into
Conversation
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
nchapma2
approved these changes
May 20, 2026
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.
What and why?
Large builds can generate enough metrics to exceed the Datadog API's payload size limit, resulting in
HTTP 413 Payload Too Largeerrors.How?
Split the metrics array into batches of 500 before sending, and fire them all in parallel with
Promise.all. Single-batch builds are unaffected; larger ones get chunked automatically.