Alexey Artamonov b3103af693 docs(observability): add a distributed tracing guide ...

Tracing reaches a workload only if it is instrumented and pointed at
the collector, and the managed engines push no OTLP spans of their
own, so operators and tenants need one place that says what the
platform provides and what is left to the application: the in-namespace
OTLP endpoints and the standard OTEL_* variables, sampling and
redaction, and what each engine can and cannot emit.

Shared-central tracing has more to it than the Tenant field description
can carry, since that text is shown as field help in the dashboard:
hosting the store in tenant-root, the shared disk and the per-tenant
write rate with its limits, the write-only and read-only logins and the
trust boundary, the windows on turning it on and off, and the order to
stop hosting in. The guide holds that detail.

Signed-off-by: Alexey Artamonov <aleksei.artamonov@aenix.io>

2026-10-06 14:34:55 +03:00

..

distributed-tracing.md

docs(observability): add a distributed tracing guide

2026-10-06 14:34:55 +03:00