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
Currently the duration of an operation in Trace Graph view is calculating as a sum of the invocations of this operation. It works incorrectly in the case of overlapping spans and leads to the situation where the duration of a child can be greater than the duration of its parent. My proposal is to calculate the duration of the union of the spans like we do for child nodes.
Expected that the duration of a node is not greater than the duration of its parent.
The total duration for overlapping spans should be the duration of their union, but not the sum.
Relevant log output
No response
Screenshot
Additional context
No response
Jaeger backend version
No response
SDK
No response
Pipeline
No response
Stogage backend
No response
Operating system
No response
Deployment model
No response
Deployment configs
No response
The text was updated successfully, but these errors were encountered:
Resolvesjaegertracing#1918
Now the total duration is calculating as
the duration of the union of spans.
Signed-off-by: Maksim Gaponov <[email protected]>
What happened?
Currently the duration of an operation in Trace Graph view is calculating as a sum of the invocations of this operation. It works incorrectly in the case of overlapping spans and leads to the situation where the duration of a child can be greater than the duration of its parent. My proposal is to calculate the duration of the union of the spans like we do for child nodes.
Steps to reproduce
Expected behavior
Expected that the duration of a node is not greater than the duration of its parent.
The total duration for overlapping spans should be the duration of their union, but not the sum.
Relevant log output
No response
Screenshot
Additional context
No response
Jaeger backend version
No response
SDK
No response
Pipeline
No response
Stogage backend
No response
Operating system
No response
Deployment model
No response
Deployment configs
No response
The text was updated successfully, but these errors were encountered: