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
{{ message }}
Repository navigation
Commit b0e6fba
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: docs/introduction/configuration.md
+6-2Lines changed: 6 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -210,7 +210,11 @@ Additional parameters:
210
210
-`opentelemetry_instrumentors` - a list of extra instrumentors.
211
211
-`opentelemetry_log_traces` - traces will be logged to stdout.
212
212
-`opentelemetry_sampler` - an `opentelemetry.sdk.trace.sampling.Sampler` deciding which traces are recorded. Unset, the SDK's own default applies: `parentbased_always_on`, which records every trace that is not the child of a non-recording remote parent, unless `OTEL_TRACES_SAMPLER` / `OTEL_TRACES_SAMPLER_ARG` say otherwise.
213
-
-`opentelemetry_generate_health_check_spans` - generate spans for health check handlers if `True`.
213
+
-`opentelemetry_generate_health_check_spans` - trace health-check requests. Defaults to `False`
214
+
since 2.0, so a probe sends no trace, the same as the access log, which never records the
215
+
health-check path. While it is `False`, OpenTelemetry's HTTP metrics also leave health-check
216
+
requests out, because the instrumentation skips an excluded URL entirely. Set it to `True` to
217
+
trace probes, for example to watch their latency.
214
218
-`opentelemetry_excluded_urls` - extra regexes for URLs excluded from tracing; the metrics path and (unless health-check spans are enabled) the health-check path are excluded automatically. Litestar searches them in the request path, FastAPI and FastMCP in the full URL. The environment variable OpenTelemetry defines for the framework (`OTEL_PYTHON_LITESTAR_EXCLUDED_URLS`, `OTEL_PYTHON_FASTAPI_EXCLUDED_URLS` or `OTEL_PYTHON_STARLETTE_EXCLUDED_URLS` for FastMCP), falling back to `OTEL_PYTHON_EXCLUDED_URLS`, adds to them.
215
219
-`opentelemetry_metrics_endpoint` - will be passed to `OTLPMetricExporter` as endpoint, and turns on the metrics signal. Its own field rather than a flag on `opentelemetry_endpoint`, so upgrading never starts exporting metrics you did not ask for. Under `opentelemetry_exporter_protocol="http"` this is a full URL (e.g. `http://collector:4318/v1/metrics`); `opentelemetry_exporter_protocol` and `opentelemetry_insecure` are shared with traces.
216
220
@@ -265,7 +269,7 @@ For FastStream there is additionally:
265
269
`faststream.redis.opentelemetry.RedisTelemetryMiddleware`, or a mapping from broker class to
266
270
middleware class (see [multiple brokers](../integrations/faststream.md#multiple-brokers)). You must
267
271
provide it to trace broker messages. Without it the rest of the configuration above still applies: the exporter is built, the
268
-
health-check span is recorded unless`opentelemetry_generate_health_check_spans` is False, and any
272
+
health-check span is recorded when`opentelemetry_generate_health_check_spans` is True, and any
0 commit comments