otel exporter for http collector endpoint #4650
Closed
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.
Tracking issue
NA
Why are the changes needed?
Currently using the otel integration requires deploying an otel collector compatible endpoint in the benchmarking environment. Managing this deployment (ie. deployment, endpoint access, etc) can add unnecessary difficulty to ad-hoc benchmarking.
What changes were proposed in this pull request?
For quick benchmarking this PR enables the file exporter to write json marhsalled protobufs to satisfy the otel http collector endpoint. The flow here is as follows:
otel_collector
file exporter in propellerHow was this patch tested?
local, cloud, etc
Setup process
Screenshots
Check all the applicable boxes
Related PRs
NA
Docs link
NA