Initial experimental support for OTLP export. #788
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
johnbley
approved these changes
Apr 1, 2024
|
|
||
| @NonNull | ||
| private Supplier<SpanExporter> supplyOtlpExporter() { | ||
| // TODO: Do we want/need to append the auth query parameter like zipkin? |
There was a problem hiding this comment.
Presumably this will get nailed down as we collaborate with the backend team?
There was a problem hiding this comment.
Actually I got confirmation today that it works the same way, so I should update this. How about I do it in a follow-up PR?
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Adds initial support for OTLP export from Splunk Android RUM instrumentation. This is not enabled by default, and is currently incompatible with the disk buffering feature. As such, if disk buffering is abled, OTLP exporting will not work and a warning will be logged.
There are not yet any beacon endpoints that will correctly handle this data anyway, but a collector can be used to inspect the payloads.