Add AwsBatchLogProcessor and OtlpAwsLogExporter Logs Pipeline #402
+869
−6
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.
In order to support CW Logs implementation for handling LLO and adhering to their new limits in ADOT, they specifically indicated that if the log is an LLO then we would export immediately:
Furthermore they need a new header for the log object that contains all of the paths to the String leaf nodes in the log body represented in
JSON protobuf
format. Below is a representation of the consolidated Gen AI event log schema in JSON protobuf format.Description of changes:
Adds
AwsBatchLogRecordProcessor
a backwards compatible custom logs BatchProcessor which has the following invariants:exported batch is ever > 1 MB
then the batch size is always length 1Added support for estimating the size of a log record based on its body and attributes. However, because logs are represented as a self-referential data-type, the log record can potentially be very nested and complex. In order to lower the impact on performance when calculating the size of a log, a depth limit is added to how deep the log will be searched.
OTLPAwsLogExporter
: 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.Customize the auto instrumentation to use the new
AwsBatchLogRecordProcessor
Testing
AwsBatchLogRecordProcessor
to support the new LLO handling logicOtlpAwsLogExporter
to validate the new Retry and LLO header logicBy submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.