Fetch Spans to Calculate Duration in Distributed Traces Using DQL

[StrangerThing]

I'm trying to mimic the way duration of a trace is shown in the Distributed Tracing apps. I'm getting very, very close but seem to be missing something. I realize this may be slightly different depending on the application, but I'd like to know if anyone has had any success with this or if anyone from Dynatrace would like to chime in and describe how it's calculated. 

My trouble is some of the spans seem to be duplicated to represent code functions and if I don't exclude them from my query they will contribute to the overall sum of the durations.

The reason this is important is because I'd like to calculate duration of a trace, but without certain specific spans and their sub-spans. I'm trying to recreate the duration in DQL as a start.

[marco_irmer]

I think you can get the main trace if you look for spans where the span.parent_id value is not present (null). 

In its simplest form and without any additional filters, the DQL might look like this:

fetch spans
| filter isNull(span.parent_id)
| fields start_time, trace.id, dt.entity.service, endpoint.name, duration

[StrangerThing]

That doesn't seem to work because my beginning span also has a span.parent_id

[IzabelaRokita]

Hey @StrangerThing ,
I just wanted to check in and see if you still need help with this. If so, I’d be happy to look into it for you! 😊
Please let me know what works best for you.

[StrangerThing]

I've built out something that works, however I'd still like a way to differentiate between async and sync spans