From ffa9eaa1f9a7f33ea08637ac7cfef081ce31a82b Mon Sep 17 00:00:00 2001 From: Jonatas Baldin Date: Wed, 25 Mar 2020 21:30:51 +0100 Subject: [PATCH] Add more explicit instruction block about enabling tracing (#2231) --- docs/serving/accessing-traces.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/docs/serving/accessing-traces.md b/docs/serving/accessing-traces.md index 7b2ccc926..810fb6142 100644 --- a/docs/serving/accessing-traces.md +++ b/docs/serving/accessing-traces.md @@ -19,6 +19,11 @@ You can update the configuration file for tracing in [config-tracing.yaml](https 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: +```shell +kubectl -n knative-serving edit configmap config-tracing +``` + ## Zipkin In order to access request traces, you use the Zipkin visualization tool. @@ -61,5 +66,3 @@ In order to access request traces, you use the Jaeger visualization tool. traces. Click on a trace to see a detailed view of a specific call. - -