OpenTelemetry Tracing #200
Open
Conversation
This file contains hidden or 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
If additional request headers are desired inside of a trace, it should be added by the instrumentation agent.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 Open Telemetry tracing to the http server.
Here are the steps to use it during local development:
:jvm-optsin the:otelalias indeps.ednto use the path to theopentelemetry-javaagent.jarfile (currently commented out with a dummy path):otelaliasdocker run --rm -p 16686:16686 -p 4318:4318 jaegertracing/jaeger:2.11.0You can now browse to http://localhost:16686 to view the Jaeger UI. Select
fluree-serverin the "Service" drop down menu, then click "Find Traces" to view traces.Jaeger UI:
Trace view:
Span view:
