File tree Expand file tree Collapse file tree 2 files changed +5
-5
lines changed
examples/example-exemplars-tail-sampling Expand file tree Collapse file tree 2 files changed +5
-5
lines changed Original file line number Diff line number Diff line change @@ -124,7 +124,8 @@ This works for all Metrics properties.
124
124
125
125
(1) Comma separated list of allowed metric names. Only these metrics will be exposed.<br />
126
126
(2) Comma separated list of excluded metric names. These metrics will not be exposed.<br />
127
- (3) Comma separated list of prefixes. Only metrics starting with these prefixes will be exposed.<br />
127
+ (3) Comma separated list of prefixes.
128
+ Only metrics starting with these prefixes will be exposed.<br />
128
129
(4) Comma separated list of prefixes. Metrics starting with these prefixes will not be exposed.<br />
129
130
130
131
## Exporter HTTPServer Properties
Original file line number Diff line number Diff line change @@ -60,11 +60,10 @@ 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 library must make sure that the Exemplar points
64
- to a trace that is
63
+ When generating Exemplars, the Prometheus Java client library must make sure that the Exemplar
64
+ points to a trace that is
65
65
actually sampled. Otherwise, Exemplar's trace ID will not be available in the monitoring backend,
66
- i.e. the Exemplar will
67
- link to a non-existing trace ID.
66
+ i.e. the Exemplar will link to a non-existing trace ID.
68
67
69
68
With _ head-based sampling_ this works out-of-the-box: The Prometheus client library calls
70
69
OpenTelemetry's
You can’t perform that action at this time.
0 commit comments