Tracing on Kiali

Jaeger

Mon, 01 Jan 0001 00:00:00 +0000

Jaeger configuration

Jaeger is a highly recommended service because Kiali uses distributed tracing data for several features, providing an enhanced experience.

By default, Kiali will try to reach Jaeger at the GRPC-enabled URL of the form http://tracing.<istio_namespace_name>:16685/jaeger, which is the usual case if you are using the Jaeger Istio add-on. If this endpoint is unreachable, Kiali will disable features that use distributed tracing data.

If your Jaeger instance has a different service name or is installed to a different namespace, you must manually provide the endpoint where it is available, like in the following example:

Tempo

Mon, 01 Jan 0001 00:00:00 +0000

Grafana Tempo Configuration
- Using the Grafana Tempo API
- Using the Jaeger frontend with Grafana Tempo tracing backend
  - Tanka
  - Tempo Operator
Configuration table
Tempo tuning
Tempo cache
Tempo authentication configuration

Grafana Tempo Configuration

There are two possibilities to integrate Kiali with Grafana Tempo: