Yuna Verheyden

I'm going to reopen, this is something we should fix.

The previous version of Tempo you were running is all the way back from December 2020: https://github.com/grafana/tempo/commit/1e8583d9a108496a35c235bb6a95ede860aff5b9. Since this version is from 1,5 years ago, it's hard to tell what...

Hi! Yes, we've called this feature _service graphs_. The Grafana Agent and the latest builds of Tempo can generate metrics which are used by Grafana to draw service graphs. We...

#860 is about ingesting really large traces, you are encountering this error while querying. It's the same issue, but it's happening in a different location. We also use GRPC between...

> Determine why coldstart is faster than reusing existing function instances I wonder if this might be a garbage collection issue? After the execution the function is frozen and garbage...

From a glance, I can't really see why this would trip up the service graphs processor. I will have to write a test and dig a bit deeper into how...

Hi, glad you're trying out Tempo! This is an unfortunate conflict between conventions from OpenTelemetry and OpenTracing and also a consequence of how Tempo search is implemented... 1. Why we...

Okay, I think we are not cleaning up resources properly after running into an error. The remote write config is loaded after the WAL has been created: https://github.com/grafana/tempo/blob/f883e844aeef2b21bc9567ac09eddcc227a9ae2e/modules/generator/storage/instance.go#L66-L69 If this...

So this is an issue upstream in Prometheus: if the first attempt to create the remote write structure fails, not all resources are cleaned up correctly and the second attempt...

We create these structures when we first receive data for that tenant. Since we don't know in advance which tenants are active, we can't create them at startup. We can...