-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature: Distributed Tracing Support #1944
Comments
Thank you for your suggestion. While I appreciate your ideas, my schedule is quite tight at the moment. Would it be possible for you to communicate with our developers on Slack? Our Slack channel is under the name |
|
This issue is available for anyone to work on. Make sure to reference this issue in your pull request. ✨ Thank you for your contribution! ✨ |
/accept |
@cubxxw Glad to see you accepted this issue🤲, this issue has been assigned to you. I set the milestones for this issue to , We are looking forward to your PR! |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
This issue was closed because it has been stalled for 7 days with no activity. |
Checklist
Is this feature request related to a problem?
✅ Yes
Problem Description
I have encountered several sdk-core crash, and it is VERY DIFFICULT to locate root cause. It's the same for server side.
Currently we have operationID param, but it's no use.
Solution Description
My organization currently uses Jaeger + Opentelementry solution. Effectiveness has been confirmed. Jaeger supports Docker/K8s deployments, and works well with Prometheus.
https://www.jaegertracing.io/docs/1.21/opentelemetry/
Benefits
Distributed context propagation
Distributed transaction monitoring
Root cause analysis
Service dependency analysis
Performance / latency optimization
Potential Drawbacks
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: