You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Requirement - what kind of business use case are you trying to solve?
I want to display the DDG of a trace started by a batch job.
Problem - what in Jaeger blocks you from solving the requirement?
Root spans of traces started by batch job are often client spans, ie. span.kind = client, but current DDG implementation requires a server root span. If this condition is not fulfilled DDG is not shown and an error message is displayed: There are no dependencies. No traces were found that contain client and any other service where span.kind is ‘server’.
I believe client root span ares valid use cases and should be supported.
Minimal test case
Following code produces a trace matching my issue:
Trace is properly displayed in timeline and graph view:
However, DDG generation fails:
Any open questions to address
Current implementation also don't support messaging scenario, ie. producer / consumer. It's not directly related to this issue so I will fill a separate one.
Requirement - what kind of business use case are you trying to solve?
I want to display the DDG of a trace started by a batch job.
Problem - what in Jaeger blocks you from solving the requirement?
Root spans of traces started by batch job are often client spans, ie. span.kind = client, but current DDG implementation requires a server root span. If this condition is not fulfilled DDG is not shown and an error message is displayed: There are no dependencies. No traces were found that contain client and any other service where span.kind is ‘server’.
I believe client root span ares valid use cases and should be supported.
Minimal test case
Following code produces a trace matching my issue:
Trace is properly displayed in timeline and graph view:
However, DDG generation fails:
Any open questions to address
The text was updated successfully, but these errors were encountered: