Navigation :

Trace requests

Sample request traces to monitor the traffic and health of your service mesh.

Distributed tracing helps you track requests across multiple services in your distributed service mesh. Sampling the requests in your mesh can give you insight into request latency, serialization, and parallelism. For more information, see the Istio tracing documentation.

To get started, enable the default Envoy distributed tracing in your Istio installation to trace requests across your service mesh, analyze service dependencies and find bottlenecks or high latency services in your mesh. Then, use a tracing provider, such as Zipkin or Jaeger, to collect and visualize the sampled spans. For a list of supported tracing providers, see the Envoy documentation.

Install a tracing provider in your workload cluster. For example, you might follow the Istio documentation to install Zipkin.
Enable tracing when you install or update Istio. The following example meshConfig options set a sampling rate of 10% of requests, add a custom host request header tag to the spans, and specify Zipkin as the default tracing provider. To add these meshConfig settings to new or existing Istio installations managed by Gloo Mesh, see the [Istio lifecycle manager install or upgrade guides] /gloo-mesh-enterprise/main/setup/installation/istio/gm_managed_istio/gloo_mesh_managed/ ). To add these meshConfig settings to new or existing Istio installations that you manually created, see the manual Istio install or upgrade guides.
- For more information about the sampling rate, custom tag, and maximum path length settings, see the Istio tracing configuration docs.
- For more information about setting a tracer, see the Istio meshConfig.defaultConfig.tracing reference docs.
```
...
meshConfig:
  enableTracing: true
  defaultConfig:
    tracing:
      # Sampling rate in range of 0.0 to 100.0 with a precision of 0.01.
      # A value of 10 means that 10% of requests are sampled.
      # Default: 1
      sampling: 10
      # Add a tag to the trace span based on a literal, environment variable,
      # or client request header.
      custom_tags:
        my_tag_header:
          header:
            name: host
      # Specify the address of a default tracer, such as Zipkin
      zipkin:
         address: zipkin:9411
...
```
Begin tracing the requests in your service mesh and view the sampled spans.