This message was deleted.

@Timothy Wigginton interesting..what is the use case when the current way to filter is not ideal?

We want to demo showing the traces coming in to signoz but showing every span can be confusing. Our initial thoughts are to add an attribute to the first span that way we can filter and show all the unique transactions

I would appreciate a couple of use cases when viewing only the root span is more beneficial. The filtering conditions are generic to all spans. How should the filtering be like for your case? If any of the spans match a filter criteria, then show the root span in the results? Won't it be difficult to find the span actually matching the filtering criteria if the number of spans in a trace can go to 1000s?

Right so all of these spans are from one API call. We want to just show one span here since once you click on one of these spans you see all the other spans. Our use case is just that it would be easier to demo, is there no way to use the existing filter conditions to do so?

is there no way to use the existing filter conditions to do so?

I don't think so... what filters do you select when seeing just the root spans?

I guess we will have to tag our root spans with “root” or something along those lines. Just wanted to make sure there wasn’t something in Signoz we were missing.