Closed CodeBlanch closed 1 month ago
Attention: Patch coverage is 96.92308%
with 2 lines
in your changes missing coverage. Please review.
Project coverage is 93.22%. Comparing base (
71655ce
) to head (409bed9
). Report is 380 commits behind head on main.
Files | Patch % | Lines |
---|---|---|
...tor/Internal/Sinks/WriteDirectlyToTransportSink.cs | 95.34% | 2 Missing :warning: |
Changes
WriteDirectlyToTransportSink
logic so it sends multiple requests to OneCollector until the batch is drainedCommonSchemaJsonSerializer
logic to drop any individual item which cannot fit into the max payload sizeDetails
OneCollector is strict about the amount of data it will process. Given a batch
OneCollectorExporter
will serialize items until it reaches the max payload size. The previous behavior was it would leave anything remaining in the batch expecting to process those records as part of the next batch. This leads to dropped telemetry though because BatchExportProcessor disposes\drains the batch after calling the exporter. The fix for this isOneCollectorExporter
will now just make multiple transmissions until it has drained the batch itself. It will now also drop any single item which itself cannot fit into the max payload size.Merge requirement checklist
CHANGELOG.md
files updated for non-trivial changes