update tracing doc (#5643)

Signed-off-by: Kuat Yessenov <kuat@google.com>
This commit is contained in:
Kuat 2019-11-12 14:10:54 -08:00 committed by Istio Automation
parent 4ea1f997f0
commit 8bdc407a6e
1 changed files with 7 additions and 1 deletions

View File

@ -10,7 +10,7 @@ aliases:
Distributed tracing enables users to track a request through mesh that is distributed across multiple services.
This allows a deeper understanding about request latency, serialization and parallelism via visualization.
Istio leverages [Envoy's distributed tracing](https://www.envoyproxy.io/docs/envoy/v1.10.0/intro/arch_overview/tracing) feature
Istio leverages [Envoy's distributed tracing](https://www.envoyproxy.io/docs/envoy/v1.12.0/intro/arch_overview/observability/tracing) feature
to provide tracing integration out of the box. Specifically, Istio provides options to install various tracing backend
and configure proxies to send trace spans to them automatically.
See [Zipkin](../zipkin/), [Jaeger](../jaeger/) and [LightStep](/docs/tasks/observability/distributed-tracing/lightstep/) task docs about how Istio works with those tracing systems.
@ -31,6 +31,12 @@ To do this, an application needs to collect and propagate the following headers
* `x-b3-flags`
* `x-ot-span-context`
Additionally, tracing integrations based on [OpenCensus](https://opencensus.io/) (e.g. Stackdriver) propagate the following headers:
* `x-cloud-trace-context`
* `traceparent`
* `grpc-trace-bin`
If you look at the sample Python `productpage` service, for example,
you see that the application extracts the required headers from an HTTP request
using [OpenTracing](https://opentracing.io/) libraries: