Search results DDG looks incorrect for hotrod data

[yurishkuro]

@everett980 a bunch of edges in this graph are incorrect

[everett980]

@yurishkuro If you hit the "view traces" button on the node interactions popup do the traces show the same issue?
Thanks to recent changes there should only be one focal node if you revisit this now, but the edges themselves I'm not sure about. It's possibly they are reversed.

[yurishkuro]

I am seeing this with the latest release 1.15.1. Steps to reproduce:

1. Edit examples/hotrod/docker-compose.yml by replacing all-in-one:latest with all-in-one:1.15.1:

--- a/examples/hotrod/docker-compose.yml
+++ b/examples/hotrod/docker-compose.yml
@@ -1,7 +1,7 @@
 version: '3.7'
 services:
   jaeger:
-    image: jaegertracing/all-in-one:latest
+    image: jaegertracing/all-in-one:1.15.1
     ports:
       - "6831:6831/udp"
       - "16686:16686"

2. docker-compse up
3. open http://0.0.0.0:8080/, hit buttons 3 times
4. open http://localhost:16686/, select dispatch service, search for traces, and hit DDG button.

[everett980]

I still haven't had a chance to dig into this further, but one issue could be that we aren't filtering paths to just span.kind === 'server' like we do in the flink job.

[yurishkuro]

I don't fully agree with how flink job does it anyway, but this doesn't sound like the issue at hand, because the graphs are just wrong, arrows pointing in the wrong directions, etc.

[cykl]

I'm still experiencing the same issue with 1.6.0. Most our DDGs look bogus with impossible arrows, mixed upstream / downstream dependencies etc. I might be able to share trace JSON if that might help.

[cykl]

Is a patch release planned?

[yurishkuro]

1.17 is coming up soon jaegertracing/jaeger#2057