Skip to content
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

Closed
2 tasks done
Sylariam opened this issue Feb 22, 2024 · 8 comments
Closed
2 tasks done

Feature: Distributed Tracing Support #1944

Sylariam opened this issue Feb 22, 2024 · 8 comments
Assignees
Labels
feature Categorizes issue or PR as related to a new feature. good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.

Comments

@Sylariam
Copy link

Sylariam commented Feb 22, 2024

Checklist

  • I've searched for similar issues and couldn't find anything matching
  • I've discussed this feature request in the OpenIMSDK Slack and got positive feedback

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

@Sylariam Sylariam added the feature Categorizes issue or PR as related to a new feature. label Feb 22, 2024
@cubxxw
Copy link
Contributor

cubxxw commented Feb 22, 2024

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
Copy link
Contributor

cubxxw commented Feb 22, 2024

@Sylariam

@kubbot
Copy link
Contributor

kubbot commented Feb 22, 2024

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿


@Sylariam

@cubxxw cubxxw added the good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. label Feb 22, 2024
@kubbot
Copy link
Contributor

kubbot commented Feb 22, 2024

This issue is available for anyone to work on. Make sure to reference this issue in your pull request. ✨ Thank you for your contribution! ✨
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
Copy link
Contributor

cubxxw commented Feb 22, 2024

/accept

@openimbot
Copy link
Contributor

@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!

@kubbot
Copy link
Contributor

kubbot commented Apr 23, 2024

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
Copy link
Contributor

kubbot commented Apr 30, 2024

This issue was closed because it has been stalled for 7 days with no activity.

@kubbot kubbot closed this as not planned Won't fix, can't repro, duplicate, stale Apr 30, 2024
@github-project-automation github-project-automation bot moved this from To Do to Done in openim-powerful Apr 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Categorizes issue or PR as related to a new feature. good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
Projects
Status: Done
Development

No branches or pull requests

4 participants