istio
/
istio.io
mirror of https://github.com/istio/istio.io.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Clarify sampling rate details for 1.0 (#3186)

This commit is contained in:
Douglas Reid 2019-02-01 10:07:11 -08:00 committed by Martin Taillefer
parent a55e475dc3
commit 13167f97ea
1 changed files with 10 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
content/docs/tasks/telemetry/distributed-tracing/index.md
View File

@ -136,12 +136,16 @@ When you make downstream calls in your applications, make sure to include these
## Trace sampling
Istio captures a trace for all requests by default. For example, when
using the Bookinfo sample application above, every time you access
`/productpage` you see a corresponding trace in the Jaeger
dashboard. This sampling rate is suitable for a test or low traffic
mesh. For a high traffic mesh you can lower the trace sampling
percentage in one of two ways:
When using the demo configuration (as in this task), Istio captures a trace for all requests.
For example, when using the Bookinfo sample application above, every time you access
`/productpage` you see a corresponding trace in the Jaeger dashboard. This sampling
rate is suitable for a test or low traffic mesh, which is why it is used as the default for
the demo installs.
In other configurations, Istio defaults to generating trace spans for 1 out of every 100 requests
(sampling rate of of 1%).
You can control the trace sampling percentage in one of two ways:
* During the mesh setup, use the Helm option `pilot.traceSampling` to
set the percentage of trace sampling. See the