Yuna Verheyden

I can confirm this fixes our issue, propagation context can be injected and extracted without error now 🙂

Hi, Grafana Tempo maintainer here :wave: It would be awesome if you could use Tempo as tracing backend for Kiali. I can help out with getting to know Tempo and...

Oh, it seems I was mistaken about a OpenTelemetry query API: Jaeger added an OpenTelemetry-compatible endpoint a while back (https://github.com/jaegertracing/jaeger-idl/pull/76), this endpoint simply returns traces from Jaeger in the OpenTelemetry...

I don't mind contributing a PR to ensure we can create `remote.Storage` twice by calling `Close` in between. Just want to check first if this would be accepted 🙂

> I found a potential error may not be logged https://github.com/grafana/tempo/blob/v1.5.0/modules/generator/registry/registry.go#L209-L212 > > I can add logs here and see if any messages are printed in the next few days...

Hi, have you seen this issue reoccur after you updated the Prometheus dependency? If you don't mind, we would grateful for a PR updating Prometheus 🙂

Nice, that's great news 🙌🏻

The WAL is indeed only used for caching samples on disk before sending them, this reduces memory pressure if an outage happens. The pointer of the remote writer isn't persisted...

https://github.com/grafana/tempo/issues/1592 shouldn't be related since the metrics-generator does not do anything with Parquet. I think the way you shut down might be causing issues, when we receive the shutdown signal...

It seems another PR has updated `go.sum` in the meantime, can you rebase this PR and resolve the merge conflicts? Besides that, it's good to merge I think 🙂