-
Notifications
You must be signed in to change notification settings - Fork 7
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
Trace topology view #128
Comments
Yeah, that's one of the features I want, such like Jaeger's dependency graph:
Right, creating a data model and printing a simple graph (or just text?) from it would be the start. I'll have a look at it! |
I know the layout will likely use features like you already have in span or detail, but I thought a little about hugo rendering https://gohugo.io/content-management/diagrams/ Also, we probably need to have a zoom. e.g. if only a few services are involved, they will fit on the current columns of the terminal. Otherwise, maybe need to zoom out or allow scrolling with center anchored on last trace viewed (of any). Probably there are other ideas. cc @tacigar not sure you've seen this it has interesting challenges being a terminal UI! |
After some research, I found that mermaid-ascii might be a good choice. I will give it a few tries. |
I started to work on this in #197 . |
exciting! |
I'm closing this issue because it's implemented in #197 ! However, it is a beta feature, so if you have any issues or ideas for improvement, please let me know! |
thanks a lot and here's the first enhancement request #200 |
would be nice to be able to aggregate service dependency links and show them
This might use code similar to https://github.com/jaegertracing/jaeger/blob/eaacbf0a40da0c3d55bfeed8d6894f14dca1d4fc/plugin/storage/memory/memory.go#L96
I once wrote one in zipkin, which has more edge cases covered maybe due to duplicate client spans and endpoint change heuristics
https://github.com/openzipkin/zipkin/blob/master/zipkin/src/main/java/zipkin2/internal/DependencyLinker.java
Whatever way, I guess the first version doesn't need to be too fancy
The text was updated successfully, but these errors were encountered: