You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tail sampling is where the decision to sample a trace takes place by considering all or most of the spans within the trace. Tail Sampling gives you the option to sample your traces based on specific criteria derived from different parts of a trace, which isn’t an option with Head Sampling.
66
66
67
+
Deploy the opentelemetry collector with `tail_sampling` enabled.
# Sample 100% of traces with ERROR-ing spans (omit traces with all OK spans)
69
76
# and traces which have a duration longer than 500ms
@@ -87,11 +94,12 @@ Tail sampling is where the decision to sample a trace takes place by considering
87
94
]
88
95
```
89
96
90
-
Applying this chart will start a new collector with the tailsampling processor
97
+
Backend 1 generates random errors for player 'bene', while Backend 2 introduces random delays for player 'anusha'.
98
+
99
+
Now let's execute some requests on the app [http://localhost:4000/?player1=bene&player2=anusha](http://localhost:4000/) and see traces in the Jaeger console [http://localhost:16686/](http://localhost:16686/).
0 commit comments