Organizing or Suppressing Auto-Generated Transactions in Trace and Performance Views

[mattweberio]

Description

I've set up distributed tracing starting from a React frontend app, passing trace headers to a backend service where I use continueTrace. This process is consistent across the entire system until the trace returns to the React app, and I manually close the parent span.

In the Sentry dashboard, under the "Frontend" link, clicking "/" shows a well-structured nested trace from pageLoad through the backend. This indicates that my trace headers are working correctly and everything is connected.

However, in the "Trace (beta)" or "Performance" views, I see hundreds of automatically recorded Redis and database spans displayed as individual transactions. While these are correctly nested under the "/" link and pageLoad view, they clutter the root-level view in the "Trace (beta)" or "Performance" views.

Question

How can I prevent these child spans (e.g., Redis and DB operations) from appearing as root-level transactions in the "Trace (beta)" or "Performance" views? I’d like to keep them in the nested view under their parent transaction but remove them from being shown as individual entries at the root level.

[lforst]

Hi, do you have a link to an example of this or maybe a screenshot? I have a hard time visualizing what you are saying.