Mario

Hi @sarahsporck, thanks for the report. This was an oversight. This [PR](https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/14324) addresses the problem

Can we close this issue? This [PR](https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/14324) fixed the problem

Hi @vishnuraj555, the service graph processor has some requirement to be able to pair up spans. You can read about it [here](https://grafana.com/docs/tempo/latest/metrics-generator/service_graphs/#how-they-work). Can you confirm that your spans have the...

Hi @suraciii, thanks for reporting. Without any errors or logs, it's very difficult to know what's going on. I suspect that a loop somewhere could've have stopped (e.g. a panic...

> 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 @Exubient. Trace ingestion works a bit different than other API endpoints in Tempo. Trace ingestion is based on OpenTelemetry receivers (OTLP, jaeger, zipkin, etc), and each can support multiple...

Hi @kilian-kier. We recently [updated](https://github.com/grafana/tempo/pull/1754) `opentelemetry-proto` to v0.18.0. You need to update the submodule to that version to be up-to-date with that change, so it doesn't appear in this PR....

Hi @krishnaindani. The idea here is that we sanitise the metric labels as we build the metrics, before they're sent to the metrics backend. The generator uses a [custom registry](https://github.com/grafana/tempo/tree/main/modules/generator/registry)...

Hi @chenfeilee! The Grafana Agent uses Prometheus Service Discovery to get metadata from Kubernetes. It should be possible to drop `Succeeded` pods using PromSD config. When using [`role: pod`](https://prometheus.io/docs/prometheus/latest/configuration/configuration/#pod), there...

That's great to hear! >One question though: do I have to drop the Failed pods too to avoid the same issue? or the same issue only occurs to Succeeded pods?...