Skip to content

Commit

Permalink
Explain how to disable self-tracing (#813)
Browse files Browse the repository at this point in the history
## Which problem is this PR solving?
- Resolves #394 again (regression in v2 docs)

## Description of the changes
- Explain `OTEL_TRACES_SAMPLER=always_off` environment variable.

Signed-off-by: Yuri Shkuro <[email protected]>
  • Loading branch information
yurishkuro authored Dec 10, 2024
1 parent db5829a commit 0ad71e5
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 0 deletions.
2 changes: 2 additions & 0 deletions content/docs/2.1/monitoring.md
Original file line number Diff line number Diff line change
Expand Up @@ -47,3 +47,5 @@ Logs by default go to `stderr` in plain text format. For production deployment l
## Traces

Jaeger has the ability to trace some of its own components, namely the requests to the Query service. For example, if you start `all-in-one` as described in [Getting Started](../getting-started/), and refresh the UI screen a few times, you will see `jaeger` populated in the Services dropdown.

Self-tracing can be disabled by setting `OTEL_TRACES_SAMPLER=always_off` environment variable.
2 changes: 2 additions & 0 deletions content/docs/next-release-v2/monitoring.md
Original file line number Diff line number Diff line change
Expand Up @@ -47,3 +47,5 @@ Logs by default go to `stderr` in plain text format. For production deployment l
## Traces

Jaeger has the ability to trace some of its own components, namely the requests to the Query service. For example, if you start `all-in-one` as described in [Getting Started](../getting-started/), and refresh the UI screen a few times, you will see `jaeger` populated in the Services dropdown.

Self-tracing can be disabled by setting `OTEL_TRACES_SAMPLER=always_off` environment variable.

0 comments on commit 0ad71e5

Please sign in to comment.