Distributed Tracing / Jaeger
Below are some commonly used configuration options for Kiali’s Jaeger integration for Tracing.
For advanced tracing integration, you can also refer to the Kiali CR
external_services.tracing section. For Helm installations, it is valid for the config map as well.
In order to fully integrate with Jaeger, Kiali needs a URL that can be resolved from inside the cluster, typically using Kubernetes DNS. This is the
in_cluster_url configuration. For instance, for a Jaeger service named
istio-system namespace, Kiali config would be:
external_services: tracing: in_cluster_url: 'http://tracing.istio-system/jaeger'
in_cluster_urlso you wouldn’t have to change anything. If you don’t use the Kiali operator, this config can be set in Kiali config map.
When not using an In-Cluster configuration, Kiali can be configuring with an external URL. This can be useful, for example, if Jaeger is not accessible from the Kiali pod. Doing so will enable links from Kiali to the Jaeger UI. This URL needs to be accessible from the browser (it’s used for links generation). Example:
external_services: tracing: in_cluster_url: 'http://tracing.istio-system/jaeger' url: 'http://my-jaeger-host/jaeger'
in_cluster_url, Kiali will not be able to show its native tracing charts, but instead will display external links to the Jaeger UI.
Once this URL is set, Kiali will show an additional item to the main menu: