https://community.dynatrace.com/t5/Dashboarding/Enable-Span-Filtering-and-Saved-Filters-in-Distributed-Tracing/m-p/304953#M5901 <DIV><H2>Problem</H2><P>When analyzing distributed traces in Dynatrace, the waterfall view can become difficult to read because it displays all spans captured within a trace, including infrastructure and client transport calls.</P><P>For example, traces often contain:</P><UL><LI>HTTP client calls to metadata services</LI><LI>Service-to-service transport spans</LI><LI>SDK/framework-generated client spans</LI><LI>AI platform/API client calls such as *.aiplatform.googleapis.com</LI></UL><P>These spans are valuable for troubleshooting and should remain stored and searchable. However, during day-to-day root cause analysis they frequently add visual noise and make it harder to focus on the business transaction flow.</P><H2>Requested Enhancement</H2><P>Add filtering capabilities directly within the Distributed Tracing waterfall view, allowing users to:</P><H3>Filter spans by</H3><UL><LI>Span kind (Client, Server, Internal, Producer, Consumer)</LI><LI>Span name</LI><LI>Service name</LI><LI>URL or endpoint pattern</LI><LI>Custom span attributes/tags</LI></UL><H3>Hide spans without deleting data</H3><P>Users should be able to temporarily hide matching spans from the waterfall visualization while preserving the underlying trace data.</P><P>Examples:</P><UL><LI>Hide all Client spans</LI><LI>Hide spans where URL contains ###.###.#######</LI><LI>Hide spans where URL contains ###.###.###.###</LI><LI>Hide transport or framework-generated spans</LI><LI>Create custom include/exclude rules</LI></UL><H3>Save Filter Preferences</H3><P>Allow users to:</P><UL><LI>Save personal filter configurations</LI><LI>Reuse filters across trace investigations</LI><LI>Set a default waterfall filter that is automatically applied when opening traces</LI></UL><H2>Expected Benefits</H2><UL><LI>Improved trace readability</LI><LI>Faster root cause analysis</LI><LI>Reduced visual clutter in complex distributed traces</LI><LI>Better user experience without sacrificing observability data</LI><LI>No need to rely on external queries or separate span views for common filtering use cases</LI></UL><H2>Important Note</H2><P>This request is <STRONG>not</STRONG> about dropping, sampling, or removing spans from ingestion. The goal is only to provide a visualization-layer filter in the waterfall view while retaining complete trace data for later investigation.</P></DIV> Thu, 01 Oct 2026 14:33:15 GMT AneesVP 2026-10-01T14:33:15Z https://community.dynatrace.com/t5/Dashboarding/Enable-Span-Filtering-and-Saved-Filters-in-Distributed-Tracing/m-p/304953#M5901 <DIV><H2>Problem</H2><P>When analyzing distributed traces in Dynatrace, the waterfall view can become difficult to read because it displays all spans captured within a trace, including infrastructure and client transport calls.</P><P>For example, traces often contain:</P><UL><LI>HTTP client calls to metadata services</LI><LI>Service-to-service transport spans</LI><LI>SDK/framework-generated client spans</LI><LI>AI platform/API client calls such as *.aiplatform.googleapis.com</LI></UL><P>These spans are valuable for troubleshooting and should remain stored and searchable. However, during day-to-day root cause analysis they frequently add visual noise and make it harder to focus on the business transaction flow.</P><H2>Requested Enhancement</H2><P>Add filtering capabilities directly within the Distributed Tracing waterfall view, allowing users to:</P><H3>Filter spans by</H3><UL><LI>Span kind (Client, Server, Internal, Producer, Consumer)</LI><LI>Span name</LI><LI>Service name</LI><LI>URL or endpoint pattern</LI><LI>Custom span attributes/tags</LI></UL><H3>Hide spans without deleting data</H3><P>Users should be able to temporarily hide matching spans from the waterfall visualization while preserving the underlying trace data.</P><P>Examples:</P><UL><LI>Hide all Client spans</LI><LI>Hide spans where URL contains ###.###.#######</LI><LI>Hide spans where URL contains ###.###.###.###</LI><LI>Hide transport or framework-generated spans</LI><LI>Create custom include/exclude rules</LI></UL><H3>Save Filter Preferences</H3><P>Allow users to:</P><UL><LI>Save personal filter configurations</LI><LI>Reuse filters across trace investigations</LI><LI>Set a default waterfall filter that is automatically applied when opening traces</LI></UL><H2>Expected Benefits</H2><UL><LI>Improved trace readability</LI><LI>Faster root cause analysis</LI><LI>Reduced visual clutter in complex distributed traces</LI><LI>Better user experience without sacrificing observability data</LI><LI>No need to rely on external queries or separate span views for common filtering use cases</LI></UL><H2>Important Note</H2><P>This request is <STRONG>not</STRONG> about dropping, sampling, or removing spans from ingestion. The goal is only to provide a visualization-layer filter in the waterfall view while retaining complete trace data for later investigation.</P></DIV> Thu, 01 Oct 2026 14:33:15 GMT https://community.dynatrace.com/t5/Dashboarding/Enable-Span-Filtering-and-Saved-Filters-in-Distributed-Tracing/m-p/304953#M5901 AneesVP 2026-10-01T14:33:15Z