Check Tempo works with kiali with jaeger-query

[aljesusg]

Check Tempo works with kiali with jaeger-query

Related with #4278 (comment)

[iblancasa]

I can help with this

[jshaughn]

@iblancasa Are you still planning to help here?

[batazor]

@jshaughn At the moment, I don't see a problem with Kiali working with Grafana-tempo, but I think switching to open telemetry would be a good step in any case.

[iblancasa]

Yes Jay. I’ll add some documentation this week. Sorry for the delay. Thanks! El El lun, 17 abr 2023 a las 15:45, Victor Login ***@***.***> escribió:

…

@jshaughn <https://github.com/jshaughn> At the moment, I don't see a problem with Kiali working with Grafana-tempo, but I think switching to open telemetry would be a good step in any case. — Reply to this email directly, view it on GitHub <#5848 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABEVNJ22VZZKPGW5DHWXH2LXBVCPLANCNFSM6AAAAAAU56MCRA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[iblancasa]

I created this repository to automatize my test: https://github.com/iblancasa/kiali-tempo-poc
There are some things that can be improved (like the Ingress for the Jaeger UI) but the important thing is tested.

What is needed to use Kiali with Grafana Tempo?

1. I followed the instructions from the official Tempo website to deploy Grafana Tempo in a kind cluster.
2. I had to do some modifications to:
   2.1. Decrease resource usage in order to be able to run the environment on my machine
   2.2. Expose the Zipkin collector
   2.3 Expose the GRPC Jaeger Query port
3. When starting istio, specify the address where my Tempo Distributor component was deployed using --set meshConfig.defaultConfig.tracing.zipkin.address=distributor.tempo.svc.cluster.local:9411 (documentation)
4. Specify the .external_services.tracing.in_cluster_url to the Jaeger Query GRPC endpoint .external_services.tracing.in_cluster_url to one Ingress route I created

I deployed the bookinfo application to ensure everything works properly.

Instead of exposing the Zipkin collector in Tempo, another option would be: to create an OpenTelemetry Collector to receive the traces and export them in OTLP format to Tempo.

@jshaughn if you want, I can try to simplify the automation from the repository and add it to the hack folder. Or just write some documentation somewhere if this comment is not enough.

Sorry for the delay and thanks!

[jshaughn]

Thanks @iblancasa! @aljesusg, how should we proceed here, documentation on the steps necessary to use Tempo, or something more formal?

[jshaughn]

Hi @iblancasa , I think what we will want to do is turn this information into content for kiali.io. Probably in this section: https://kiali.io/docs/configuration/p8s-jaeger-grafana/jaeger/.

[iblancasa]

Awesome. In that case, I'll create a PR to the kiali.io repository as soon as I can :)

[jshaughn]

Sounds great, if you need any guidance let us know.

[Hronom]

Please can we add it?

[Hronom]

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

[caerulescens]

I managed to get this all working with the latest version of the tempo-distributed chart by working from @Hronom and @iblancasa instructions. Thanks guys

[aljesusg]

Thabks to verify.
Anyway @josunect did a demo in kiali.io you will see it soon

You can check the preview here https://deploy-preview-686--kiali.netlify.app/docs/tutorials/tempo/

Please feel free to add more information about it 🙏

[caerulescens]

Sure thing. I looked over the docs, and that's about the same thing I had to do. Create a PVC for MinIO and connect Tempo. Although, I'm doing it all through Helm managed by ArgoCD.

[aljesusg]

Great !!! If you find any problem with argocd please let us know or if you prefer we can help you to contribute to the project with a tutorial about it 🤗

[aljesusg]

Added tutorial to kiali.io