[WIP] Support for handling LLO in OTLP AWS Logs Exporter #363
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.
Supporting ADOT auto instrumentation to handle LLO log events.
Description of changes:
AwsBatchLogRecordProcessora backwards compatible custom logs BatchProcessor which has the following invariants:exported batch is ever > 1 MBthen the batch size is always length 1OTLPAwsLogExporter: Adds a new behavior for Retry delay based on server-side response of Retry-After header. Injects the LLO header flag if the size of the exported data > 1 MB.AwsBatchLogRecordProcessorTesting:
TODO:
AwsBatchLogRecordProcessorandOTLPAwsLogExporterBy submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.