Tempo Support

[aljesusg]

Tempo Support

Alpha - Users able to configure for Tempo

• kiali.io docs: Tempo Operator (Add steps to use Tempo as tracing storage via Tempo operator kiali.io#677)
• kiali.io docs: Tempo Helm Charts
• kiali.io docs: Tempo docs approach (Update tempo docs kiali.io#735)

Beta

• Check Tempo works with kiali with jaeger-query #5848
• Use Opentelementry Exporter instead of Jaeger #5569
• Support tempo reading traces #5849
• Tempo support improvements #6538

[rlex]

it's worth mentioning that jaeger-query as part of tempo is outdated and basically deprecated

[jshaughn]

@aljesusg , Do we need to redefine the issues here? Is there some action we can take at this point? If there is nothing to do we can drop this from the sprint backlog or set to waiting-external?

[Hronom]

Sad story, no movements so far, but also of discussions here.
I hope Grafana will support all functionality that Kiali has, so we can drop Kiali.

Primarily interested in graph of services

[aljesusg]

Hi @Hronom

You can follow these instructions to use tempo in kiali

#5848 (comment)

[jmazzitelli]

I hope Grafana will support all functionality that Kiali has, so we can drop Kiali.

Then you should submit an issue to the Grafana project team if you want them to support all functionality that Kiali has. Asking for that in the Kiali github project isn't going to get what you want. You should make that request directly to the Grafana folks.

[jshaughn]

Yes, good luck with Grafana! And thanks for your contribution!

[Hronom]

I'm trying to find how to use Tempo and Kiali together. I also see no solution here and I see discussion without results. This is frustrating especially after you read full thread here.

I also found that tempo-query plugin(which was proposed to use in workaround) not works.
It expected that it not works anymore, since Grafana plans to deprecate it.
Back in time, it was created to support tempo in Grafana trough Jaeger API, but now Grafana got official support for Tempo, so this tempo-query not needed anymore.

If I had knowledge of Kiali codebase(I believe maintainers know it) I think it will be simple for me to add support for it.
Tempo REST API description is here https://grafana.com/docs/tempo/latest/api_docs/#search
When it goes to retrieve traces, the API looks similar to what Jaeger has.

As of today you can easily push traces from Istio into Tempo trough OpenTelemetry.

But unfortunately Kialy not supports Tempo.

And again I don't see movements here #5849

[Hronom]

Finally manage it to work, here is temporary workaround until support of Tempo not added directly to Kiali