Mario

Ups, it seems the `logQueryRequestHeaders` wasn't correctly updated everywhere. When that's fixed I'll merge cc/ @jmichalek132

> If I raised a PR for it would it be welcomed? Yes! I'll assign you the issue.

Agree this would be a nice addition. It's been discussed in the past, but never implemented. This requires changes in the connector and in the visualisations (AFAIK, Grafana). For the...

Hi @97amarnathk. Thanks for the interest, unfortunately, I'm already working on this issue. Apologies for not noting it here, my bad. Although I'm sure there'll be plenty of tasks that...

> Oh actually reading this more closely, what you're saying you won't support out of the gate is filtering for a query like `{cluster=foo} && {environment=dev}`. You would support `{cluster=foo...

>Will I be able to use autocomplete to tell me that? I think the answer is yes, but not via the search tags endpoint, but probably through search tag values?...

Superseded by https://github.com/grafana/tempo/issues/2957

Hi @liamoddell. Tempo search is [non-deterministic](https://grafana.com/docs/tempo/latest/getting-started/tempo-in-grafana/#non-deterministic-search), which means that Tempo will return the first results that it finds, without a preference to more recent traces. Related issue: https://github.com/grafana/tempo/issues/2476

Hi @luxaritas. This is a good suggestion but there are a couple of things to consider to support this. Right now, Tempo depends on two main conditions to detect nodes/edges...

Hi! It seems like the path to Tempo is not correctly configured. Does trace by ID work? Or does it fail with 404 as well? Can you check if you're...