Certain queries don't autofill the values drop down in the filter

[alexbikfalvi]

Problem

When entering certain queries in the Explore Traces filter, the filter doesn't show a drop down with options for certain attributes (for example certain span attributes).

Even though the same query does generate a list of options in classic Explore.

Furthermore, when the values drop down is not shown, the user doesn't have the possibility to type the query.

[adrapereira]

There's actually one more filter in place in Explore Traces which is affecting the difference in results. If you look closely you'll see that the primary signal in Explore Traces is Full traces, which generates an additional filter for all queries nestedSetParent = -1, which means that it's only looking for top level spans.

Try changing the primary signal to All spans and check whether the results match what you see in Explore classic.

[alexbikfalvi]

There's actually one more filter in place in Explore Traces which is affecting the difference in results. If you look closely you'll see that the primary signal in Explore Traces is Full traces, which generates an additional filter for all queries nestedSetParent = -1, which means that it's only looking for top level spans.

Try changing the primary signal to All spans and check whether the results match what you see in Explore classic.

@adrapereira You're correct: using that option all values appear in the drop down. So it's more of a usability issue then - without knowing you have to pick that option, it's confusing that the attribute appears but the values don't.