DEBUG-3558 DI: chunk snapshot payloads

[p-datadog]

What does this PR do?
Implements chunking of dynamic instrumentation snapshot payloads to stay under the 10 MB intake limit.

Motivation:
Without chunking, if a probe (or multiple probes) produce many events, all of the events will be dropped by the intake.

Change log entry
Yes: dynamic instrumentation: fix sending large quantities of snapshots

Additional Notes:
There is also "snapshot pruning" which is supposed to be done to reduce the size of individual snapshot events below the 1 MB limit for a "log line". This is not in scope for this PR (or Ruby Live Debugger GA).

This PR ensures that if many events are generated by Live Debugger, they all get sent to the backend, but does not help with huge individual snapshots getting dropped.

This PR does however add diagnostics when snapshots are dropped due to excessive size.

How to test the change?
Unit tests added

[github-actions]

Thank you for updating Change log entry section 👏

^{Visited at: 2025-11-24 18:05:19 UTC}

[pr-commenter]

Benchmarks

Benchmark execution time: 2025-12-01 21:28:30

Comparing candidate commit 5390e30 in PR branch di-chunk with baseline commit 18e70e4 in branch master.

Found 1 performance improvements and 1 performance regressions! Performance is the same for 42 metrics, 2 unstable metrics.

scenario:profiling - Allocations ()

• 🟩 throughput [+239921.346op/s; +276924.446op/s] or [+8.071%; +9.315%]

scenario:tracing - Propagation - Trace Context

• 🟥 throughput [-4060.371op/s; -3952.700op/s] or [-10.860%; -10.572%]

[github-actions]

Typing analysis

Note: Ignored files are excluded from the next sections.

Untyped methods

This PR introduces 4 untyped methods, and clears 3 untyped methods. It decreases the percentage of typed methods from 54.94% to 54.93% (-0.01%).

Untyped methods (+4-3)

❌ Introduced:

sig/datadog/di/transport/input.rbs:37
└── def initialize: (untyped apis, untyped default_api, logger: untyped) -> void
sig/datadog/di/transport/input.rbs:39
└── def current_api: () -> untyped
sig/datadog/di/transport/input.rbs:41
└── def send_input: (untyped payload, untyped tags) -> untyped
sig/datadog/di/transport/input.rbs:43
└── def send_input_chunk: (untyped chunked_payload, untyped serialized_tags) -> untyped

✅ Cleared:

sig/datadog/di/transport/input.rbs:34
└── def initialize: (untyped apis, untyped default_api, logger: untyped) -> void
sig/datadog/di/transport/input.rbs:36
└── def current_api: () -> untyped
sig/datadog/di/transport/input.rbs:38
└── def send_input: (untyped payload, untyped tags) -> untyped

If you believe a method or an attribute is rightfully untyped or partially typed, you can add # untyped:accept to the end of the line to remove it from the stats.

[datadog-official]

✅ Tests

🎉 All green!

❄️ No new flaky tests detected
🧪 All tests passed

🎯 Code Coverage
• Patch Coverage: 93.98%
• Total Coverage: 95.16% (+0.00%)

View detailed report

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 5390e30 | Docs | Datadog PR Page | Was this helpful? Give us feedback!}

[p-datadog]

I got the limits wrong in the initial implementation of this PR, this has now been corrected.

[Strech]

Have a tiny suggestion over performance of the filter_map

[Strech]

I've left the suggestion about the filter_map path when it's not lazy enumerator