https://community.dynatrace.com/t5/Open-Q-A/Distributed-tracing-filter-requests-by-child-span-attributes/m-p/277730#M36561 <P>In gen2 (classic view) with OA traces it is possible via backtraces/service flow feature. Currently this feature is not available as gen3 app for Opentelemetry spans, but probably it will be in future.<BR /><BR />Via DQL this is feasible, you need to perform a query like this:<BR />(note: it is for DB queries, but you can replicate the logic)</P><LI-CODE lang="markup">fetch spans | filter db.namespace == "DB1" | filter code.function == "executeQuery" | filter duration &gt; 100ms | fields start_time, Service = entityName(dt.entity.service), Database = db.namespace, Query = db.query.text, QueryTime = duration, trace.id, subtrace.id, span.id | join [fetch spans | filter isNotNull(duration) and isNotNull(endpoint.name) | summarize { child_requests = arrayRemoveNulls(collectDistinct( record( endpoint.name, duration )))}, by: {trace.id, subtrace.id} ], kind: leftOuter, on: {subtrace.id}, executionOrder:leftFirst | expand right.child_requests | fields start_time, Service, EndPoint = right.child_requests[endpoint.name], Duration = right.child_requests[duration], Database, Query, QueryTime, trace.id, span.id | sort QueryTime desc | filterOut isNull(EndPoint) | summarize { requestCount = count(), avgQueryTime = avg(QueryTime), avg(Duration), collectDistinct(concat(Service, "|", EndPoint)) }, by: {Query} //| filter requestCount &gt; 100 | sort avgQueryTime desc</LI-CODE><P>&nbsp;</P> Wed, 21 May 2025 20:00:38 GMT yanezza 2025-05-21T20:00:38Z https://community.dynatrace.com/t5/Open-Q-A/Distributed-tracing-filter-requests-by-child-span-attributes/m-p/277184#M36510 <P>Hi, I am new to Dynatrace and I would like to know if there is a way, in the&nbsp;<STRONG>Dynamic Tracing </STRONG>app, to show all the requests with a nested child span that has a specific attribute. I am currently using OpenTelemetry ingestion, and the closest i was able to get to that is to select "Span" view instead of "Requests", and then the filter input shows me all the span attributes.</P><P>EDIT: Another way I obtained the same result, was to manually add each attribute that I wanted to track to both the current span and the root span (walking the span tree upwards) in my program, but this solution is useless if the trace was started by another services.</P> Wed, 14 May 2025 12:22:34 GMT https://community.dynatrace.com/t5/Open-Q-A/Distributed-tracing-filter-requests-by-child-span-attributes/m-p/277184#M36510 matcap 2025-05-14T12:22:34Z https://community.dynatrace.com/t5/Open-Q-A/Distributed-tracing-filter-requests-by-child-span-attributes/m-p/277730#M36561 <P>In gen2 (classic view) with OA traces it is possible via backtraces/service flow feature. Currently this feature is not available as gen3 app for Opentelemetry spans, but probably it will be in future.<BR /><BR />Via DQL this is feasible, you need to perform a query like this:<BR />(note: it is for DB queries, but you can replicate the logic)</P><LI-CODE lang="markup">fetch spans | filter db.namespace == "DB1" | filter code.function == "executeQuery" | filter duration &gt; 100ms | fields start_time, Service = entityName(dt.entity.service), Database = db.namespace, Query = db.query.text, QueryTime = duration, trace.id, subtrace.id, span.id | join [fetch spans | filter isNotNull(duration) and isNotNull(endpoint.name) | summarize { child_requests = arrayRemoveNulls(collectDistinct( record( endpoint.name, duration )))}, by: {trace.id, subtrace.id} ], kind: leftOuter, on: {subtrace.id}, executionOrder:leftFirst | expand right.child_requests | fields start_time, Service, EndPoint = right.child_requests[endpoint.name], Duration = right.child_requests[duration], Database, Query, QueryTime, trace.id, span.id | sort QueryTime desc | filterOut isNull(EndPoint) | summarize { requestCount = count(), avgQueryTime = avg(QueryTime), avg(Duration), collectDistinct(concat(Service, "|", EndPoint)) }, by: {Query} //| filter requestCount &gt; 100 | sort avgQueryTime desc</LI-CODE><P>&nbsp;</P> Wed, 21 May 2025 20:00:38 GMT https://community.dynatrace.com/t5/Open-Q-A/Distributed-tracing-filter-requests-by-child-span-attributes/m-p/277730#M36561 yanezza 2025-05-21T20:00:38Z