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
Copy file name to clipboardExpand all lines: examples/example-exemplars-tail-sampling/README.md
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -60,7 +60,7 @@ There are two ways how to do this:
60
60
2._Tail-based sampling_ is performed by an external infrastructure component like
61
61
the [OpenTelemetry collector](https://opentelemetry.io/docs/collector/).
62
62
63
-
When generating Exemplars, the Prometheus Java client libray must make sure that the Exemplar points
63
+
When generating Exemplars, the Prometheus Java client library must make sure that the Exemplar points
64
64
to a trace that is
65
65
actually sampled. Otherwise, Exemplar's trace ID will not be available in the monitoring backend,
66
66
i.e. the Exemplar will
@@ -95,10 +95,10 @@ The `docker-compose` file will run the example with the following containers:
95
95
96
96
-`hello-world-app`: Java service described above, with the OpenTelemetry Java instrumentation agent
97
97
attached for
98
-
distrubted tracing.
98
+
distributed tracing.
99
99
-`greeting-service`: Java service described above, with the OpenTelemetry Java instrumentation
100
100
agent attached for
101
-
distrubted tracing.
101
+
distributed tracing.
102
102
-`collector`: OpenTelemetry collector for receiving the distributed traces, performing _tail
103
103
sampling_, and forwarding
104
104
them to `tempo`.
@@ -124,7 +124,7 @@ password _admin_.
124
124
125
125
## Example Dashboard
126
126
127
-
The example dashboard shows 50 requests / second for the Java serices:
127
+
The example dashboard shows 50 requests / second for the Java services:
128
128
129
129
<!-- editorconfig-checker-disable-line -->
0 commit comments