Mario

I like the proposal and would like to see this feature move forward, but have some thought regarding the generated metrics: I'm not convinced that events are a great candidate...

Sure. Some filtering could help with cardinality in general 👍 I can see both allowlists and denylists being useful here. Probably we should think how #1482 could help events as...

I think we can close this issue as we're not following this list. Feel free to re-open or tackle any of the items still left to be completed.

Done in https://github.com/grafana/tempo/pull/2253. Additional work can be tracked in https://github.com/grafana/tempo/issues/1868.

``` goos: darwin goarch: arm64 pkg: github.com/grafana/tempo/tempodb/encoding/vparquet3 │ old.txt │ new.txt │ │ sec/op │ sec/op vs base │ BackendBlockQueryRange/{}_|_rate()/1-12 82.08m ± 0% 80.75m ± 1% -1.61% (p=0.002 n=6) BackendBlockQueryRange/{}_|_rate()/2-12...

The highest cardinality attribute that I could find was `span.http.url`, which has up to 14k unique values. This are the benchmarks for that attribute: Benchmark results ``` goos: darwin goarch:...

Likely related https://github.com/grafana/loki/issues/4483

The compactor, as many other Tempo components, uses memberlist to coordinate across instances. As described in the issue I linked, the problem happens when Tempo can't find a default network...

The ring config in the ingester is slightly different than in the distributor or compactor. Try with this ```yaml ingester: lifecycler: interface_names: - enp7s0 ring: kvstore: store: etcd etcd: ......

Hi! Are you getting any errors in Tempo or is data just not being streamed? Also, the config parameter for HTTP streaming is [`stream_over_http_enabled`](https://grafana.com/docs/tempo/latest/api_docs/#tempo-grpc-api), but you shouldn't need. It should...