Grafana 7.5 with Tempo

  • What Grafana version and what operating system are you using?

7.5 / linux

  • What are you trying to achieve?

I am trying to add Tempo as a data source to Grafana.

  • How are you trying to achieve it?

  • What happened?

Everything’s ok when adding tempo as a data source (http://tempo-tempo-distributed-query-frontend.monitoring:16686) to Grafana until version 7.4.5 .
Starting from 7.5 grafana image I’m getting the following error:

“failed to convert tempo response to Otlp: proto: ExportTraceServiceRequest: wiretype end group for non-group”

I understand that accordingly to 7.5 release notes (https://grafana.com/docs/grafana/latest/whatsnew/whats-new-in-v7-5/#tempo-as-a-backend-data-source) the support for tempo-query’s (Jaeger) response was dropped, I’m pretty sure that’s related to it, but I’m not sure what am I supposed to do to move forward with this.

  • What did you expect to happen?

I would expect to add Tempo as a data source successfully

  • Did you receive any errors in the Grafana UI or in related logs? If so, please tell us exactly what they were.
grafana t=2021-06-05T16:26:14+0000 lvl=eror msg="Metric request error" logger=context userId=1 orgId=1 uname=admin error="failed to convert tempo response to Otlp: proto: ExportTraceServiceRequest: wiretype end group for non-group" remote_addr=10.123.33.253**

Hi @mfamador

Tempo 1.o just shipped along with Grafana 8 this week. Have you considered upgrading? That might solve this installation issue…

Hi! Thanks, @mattabrams ! My bad, I should have updated this thread, I solved it using the opentelemetry port instead of the Jaeger one.

http://tempo-tempo-distributed-query-frontend.monitoring:3100

1 Like