@ptodev not exactly sure if I understand the question. Tempo part is just to create the query for loki. We could probably show some sort of example query in the config page to illustrate that a bit. We basically just append |="${__span.traceId}" to the query where the ${__span.traceId} will be replaces by the actual traceId from the trace. So would a query example in the config page help?

Hello, as you may have heard, we are transitioning away from using discussions to discuss feature requests. If you can clarify what it is you're looking for, feel free to make an issue and we can go from there.

Hi, I would like this functionality clarifying too, the OP question is very clear to me. It matches my scenario too. It is not clear precisely how the matching logic works given the generated query. i,.e when you try Filter by Span Id, i get bupkiss, nada, nothing. So a clear explaination of how these two toggles work would go along way in improving the user experience of navigating very long traces.