Closed Sylariam closed 7 months ago
cubxxw
commented
9 months ago 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 k8s. Your input and collaboration would be greatly appreciated.
cubxxw
commented
9 months ago @Sylariam
kubbot
commented
9 months ago Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿
@Sylariam
kubbot
commented
9 months ago This issue is available for anyone to work on. Make sure to reference this issue in your pull request. :sparkles: Thank you for your contribution! :sparkles:
Join slack 🤖 to connect and communicate with our developers.
If you wish to accept this assignment, please leave a comment in the comments section: /accept.🎯
cubxxw
commented
9 months ago /accept
openimbot
commented
9 months ago kubbot
commented
7 months ago 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.
kubbot
commented
7 months ago 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