Memory Mode: Adding support for OTLP HTTP Exporter - Second draft #6273
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.
This PR aims to showcase how an implementation of the design explained here would look like.
The overarching goal is to minimize the memory allocations done in the OTLP HTTP exporter.
Since the protobuf definition of the entire
MetricsData
schema is large, I've only focused on everything encapsulated atKeyValueMessage
.