Accessing request traces

You can update the configuration file for tracing in config-tracing.yaml.

Follow the instructions in the file to set your configuration options. This file includes options such as sample rate (to determine what percentage of requests to trace), debug mode, and backend selection (zipkin or stackdriver).

You can quickly explore and update the ConfigMap object with the following command:

In order to access request traces, you use the Zipkin visualization tool.

1. This command starts a local proxy of Zipkin on port 8001. For security reasons, the Zipkin UI is exposed only within the cluster.

2. Access the Zipkin UI at the following URL:

   Where is the namespace where Zipkin is deployed, for example, . 1. Click “Find Traces” to see the latest traces. You can search for a trace ID or look at traces of a specific application. Click on a trace to see a detailed view of a specific call.

In order to access request traces, you use the Jaeger visualization tool.

1. Access the Jaeger UI at the following URL:

   Where is the namespace where Jaeger is deployed, for example, .

2. Select the service of interest and click “Find Traces” to see the latest traces. Click on a trace to see a detailed view of a specific call.