docs: instructions for using OpenTelemetry tracing #178
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.
What problem does this PR solve?
This PR adds complete OpenTelemetry distributed tracing configuration documentation for OpenGemini Java Client, facilitating user integration of link tracing functionality.
Changes
Configuration Features
[✓ ] Supports Jaeger as tracing backend
[✓ ] Automatically traces all database operations (queries and writes)
[✓ ] Batch processing optimizes performance
[✓ ] Service name identification for easy monitoring
Usage :
Users only need to follow the documentation steps to add dependencies and configuration code, and distributed tracing will be automatically added to all OpenGemini operations.
Testing :
Related integration tests have been verified in TracingIntegrationTest to ensure the tracing functionality works properly.
*related documents:
openGemini/openGemini.github.io#163