-
Notifications
You must be signed in to change notification settings - Fork 384
🔌 Plugin: Jeager/Zipkin #253
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
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Re-opening since plugin suggestion issues are now exempt from stalebot. |
Would be nice if there would be a complete istio plugin, which would show data from jaeger, kiali and the functionality a certain application is using from istio. Think about circuit breaking, fault injection and stuff. |
Yeah, those types of view when you get collected / correlated data from related systems gathered into one place, can be where the most value can be had for users. |
What do you think about integrating SigNoz? |
cc. @tacigar |
Are there something new? Do we have jaeger backstage plugin? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Uh oh!
There was an error while loading. Please reload this page.
Summary
Once developers find out that their application has an issue, it is very beneficial to see the application's traces. This can help identify the source of the issue.
Motivation
I am using Istio service mesh (on top of k8s) along with Jeager tracing.
I often depend on the tracing information to find the source of a particular issue or latency.
I believe that ability for developers to see traces of their application will be beneficial in diagnosing their application.
The text was updated successfully, but these errors were encountered: