fix(datadog_traces) align max payload size with DD agent

[s-maj]

Based on the change in the Datadog Agent, the current default limit is 25MB instead of 3.2MB defined currently in the Datadog Traces sink. Bumping the limit might help with the issue 14244 too.

[bits-bot]

All committers have signed the CLA.

[netlify]

✅ Deploy Preview for vrl-playground canceled.

Name	Link
🔨 Latest commit	9a03d0a
🔍 Latest deploy log	https://app.netlify.com/sites/vrl-playground/deploys/64b660b4eaf755000840f6c2

[netlify]

✅ Deploy Preview for vector-project canceled.

Name	Link
🔨 Latest commit	9a03d0a
🔍 Latest deploy log	https://app.netlify.com/sites/vector-project/deploys/64b660b41a8b830008942c2f

[neuronull]

Based on the change in the Datadog Agent, the current default limit is 25MB instead of 3.2MB defined currently in the Datadog Traces sink. Bumping the limit might help with the issue 14244 too.

👋 hello @s-maj , thanks for this suggestion.

I went a head and tried this locally sending a large trace - but the datadog_traces sink received a 413 error code.

Did you try this out yourself and I might be missing something?

It kind of reads like DataDog/datadog-agent#14782 is actually modifying the intake of traces into the trace agent , as opposed to the output. (Though, I do recognize that PR references it trying to more closely align with the DD backend, which would suggest that the backend could accept a payload larger than 3 MB).

[s-maj]

Yeah, looks like I didn't test it right. I've looked at DD agent code again and it seems the total payload going to the backend is indeed 3.2MB but the Agent can ingest much bugger payloads.

EDIT for posterity:
Chunking itself happens here and subsequently here.