Chapter 9. Integrating Red Hat OpenShift distributed tracing platform with Kiali Operator provided by Red Hat

Procedure

1. Update the Kiali resource spec configuration for tracing:

   Example Kiali resource spec configuration for tracing

   spec:
     external_services:
       grafana:
         enabled: true 1
         in_cluster_url: http://grafana-istio-system.apps-crc.testing/ 2
         url: http://grafana-istio-system.apps-crc.testing/
       tracing:
         enabled: true
         provider: tempo
         use_grpc: false
         in_cluster_url: http://tempo-sample-query-frontend.tempo:3200
         url: https://tempo-sample-query-frontend-tempo.apps-crc.testing
         tempo_config: 3
           org_id: "1"
           datasource_uid: a8d2ef1c-d31c-4de5-a90b-e7bc5252cd00

   1

   Required so that you can see the View in Tracing link from the Traces tab.

   2

   If the Tempo resource is deployed with multiple tenants, then the in_cluster_url config should point to the gateway with the tenant name as part of the URL. For example: http://tempo-resource-gateway.tempo:8080/api/traces/v1/{tenantName}/tempo

   3

   Required so that you can see the View in Tracing link from the Traces tab and redirect to the proper Tempo datasource.

2. Save the updated spec in 'kiali_cr.yaml`.

3. Run the following command to apply the configuration:

   oc patch -n istio-system kiali kiali --type merge -p "$(cat kiali_cr.yaml)"

   Output:

    kiali.kiali.io/kiali patched

Verification

1. Run the following command to get the Kiali route:

   oc get route kiali ns istio-system

2. Navigate to the Kiali UI.
3. Navigate to Workload Traces tab to see traces in the Kiali UI.