Chapter 5. Configuring tracing in Connectivity Link

Procedure

1. Enable tracing in OpenShift Service Mesh by configuring your Telemetry custom resource as follows:

   apiVersion: telemetry.istio.io/v1alpha1
   kind: Telemetry
   metadata:
     name: mesh-default
     namespace: gateway-system
   spec:
     tracing:
     - providers:
       - name: tempo-otlp
       randomSamplingPercentage: 100

   Copy to Clipboard Toggle word wrap

2. Configure a tracing extensionProvider in OpenShift Service Mesh in your Istio custom resource as follows:

   apiVersion: operator.istio.io/v1alpha1
   kind: Istio
   metadata:
     name: default
   spec:
     namespace: gateway-system
     values:
       meshConfig:
         defaultConfig:
           tracing: {}
         enableTracing: true
         extensionProviders:
         - name: tempo-otlp
           opentelemetry:
             port: 4317
             service: tempo.tempo.svc.cluster.local

   Copy to Clipboard Toggle word wrap
   Important

   You must set the OpenTelemetry collector protocol in the service port name or appProtocol fields as described in the OpenShift Service Mesh documentation. For example, when using gRPC, the port name should begin with grpc- or the appProtocol should be grpc.

3. Enable request tracing in your Authorino custom resource and send authentication and authorization traces to the central collector as follows:

   apiVersion: operator.authorino.kuadrant.io/v1beta1
   kind: Authorino
   metadata:
     name: authorino
   spec:
     tracing:
       endpoint: rpc://tempo.tempo.svc.cluster.local:4317

   Copy to Clipboard Toggle word wrap

4. Enable request tracing in your Limitador custom resource and send rate limit traces to the central collector as follows:

   apiVersion: limitador.kuadrant.io/v1alpha1
   kind: Limitador
   metadata:
     name: limitador
   spec:
     tracing:
       endpoint: rpc://tempo.tempo.svc.cluster.local:4317

   Copy to Clipboard Toggle word wrap
   Note

   Ensure that the tracing collector is the same one that OpenShift Service Mesh is sending traces to so that they can all be correlated later.

   When the changes are applied, the Authorino and Limitador components are redeployed with tracing enabled.

   Important

   Trace IDs do not propagate to Wasm modules in OpenShift Service Mesh currently. This means that requests passed to Limitador do not have the relevant parent trace ID. However, if the trace initiation point is outside Service Mesh, the parent trace ID is available to Limitador and included in traces. This impacts on correlating traces from Limitador with traces from Authorino, the Gateway, and any other components in the request path.