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

DDG for search results is still wrong #554

Closed
yurishkuro opened this issue Apr 2, 2020 · 3 comments · Fixed by #557
Closed

DDG for search results is still wrong #554

yurishkuro opened this issue Apr 2, 2020 · 3 comments · Fixed by #557

Comments

@yurishkuro
Copy link
Member

The HotROD graph is missing DB nodes. The redis and mysql services do show in the search results, as well as in the regular DAG graph, but not in DDG:

image

@rubenvp8510
Copy link
Collaborator

I'll review this one.

@rubenvp8510
Copy link
Collaborator

rubenvp8510 commented Apr 3, 2020

This happens because the transformation function filters spans to process only spans.kind = "server", it doesn't process client spans. 8cb13c4

Is that the way it should work?

@everett980 @yurishkuro

@yurishkuro
Copy link
Member Author

I think we discussed it a number of times. No, I don't think it's correct. Any transition (as in parent-child span pair) from service X to Y should result in an edge in the graph. The only value there can be in looking at span.kind is if the service is calling itself recursively, vs. just having a bunch of inner spans, in the former we want X-X edge, in the latter - no edge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants