Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion docs/content/config/config.md
Original file line number Diff line number Diff line change
Expand Up @@ -124,7 +124,8 @@ This works for all Metrics properties.

(1) Comma separated list of allowed metric names. Only these metrics will be exposed.<br/>
(2) Comma separated list of excluded metric names. These metrics will not be exposed.<br/>
(3) Comma separated list of prefixes. Only metrics starting with these prefixes will be exposed.<br/>
(3) Comma separated list of prefixes.
Only metrics starting with these prefixes will be exposed.<br/>
(4) Comma separated list of prefixes. Metrics starting with these prefixes will not be exposed.<br/>

## Exporter HTTPServer Properties
Expand Down
7 changes: 3 additions & 4 deletions examples/example-exemplars-tail-sampling/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -60,11 +60,10 @@ There are two ways how to do this:
2. _Tail-based sampling_ is performed by an external infrastructure component like
the [OpenTelemetry collector](https://opentelemetry.io/docs/collector/).

When generating Exemplars, the Prometheus Java client library must make sure that the Exemplar points
to a trace that is
When generating Exemplars, the Prometheus Java client library must make sure that the Exemplar
points to a trace that is
actually sampled. Otherwise, Exemplar's trace ID will not be available in the monitoring backend,
i.e. the Exemplar will
link to a non-existing trace ID.
i.e. the Exemplar will link to a non-existing trace ID.

With _head-based sampling_ this works out-of-the-box: The Prometheus client library calls
OpenTelemetry's
Expand Down