observability.otel.endpoint is set. With no endpoint
configured, no exporter is created and dispatch is untouched — there is zero
overhead and no dependency on a live collector.
What gets traced
When an OTLP/HTTP endpoint is configured, each tool dispatch is wrapped in a root span namedreliquary_tc.<tool> (kind SERVER). Its attributes carry the
tool name, vault id, scope class, and call status — never tool arguments,
secrets, or tokens.
observability.otel.detail controls what is emitted under the root span:
root(default): the root span only. No child span is created and nothing extra is allocated, so the default costs what it always did.children: adds one child span per pipeline stage, in order:input_parse,auth_check,policy_eval,idempotency(keyed calls),rate_limit(when a limiter is configured),hitl_check(HITL-gated calls),acl_eval,tool_impl,output_serialize.verbose: also adds abatch_itemspan per item ofread_notes,read_resourcesandsearch_and_read, anddb_transaction/db_savepoint/db_write_transactionspans for SQLite transactions. At most 64 child spans are created per request; the root carriesreliquary_tc.spans_droppedwhen the cap cut some.
Configuration
otel.endpoint unset disables tracing (no exporters, no throw).
Tracing is exercised in tests with an in-memory exporter — unconfigured asserts
zero exporters and no throw; configured asserts the span shape — so no live
collector is ever required.