POST /v1/traces endpoint.
The gateway accepts OTLP protobuf and OTLP JSON. The API key identifies the
workspace; a tenant ID in the payload does not select another workspace.
Content follows the workspace setting
In Settings → Workspace, the owner controls input and output capture separately. An exporter sending text does not override that choice. Without a known workspace choice, the workspace half is off. A gateway operator’s configured capture allowlist can also enable a half. The direct mTLS ingest receiver uses only the workspace decision; without a control plane, it drops content and keeps metadata.
Unknown string attributes require both halves to be enabled. Unknown content
families, such as prompt or completion keys without a supported typed mapping,
are dropped even when capture is on. A span’s
tracelane_content_withheld field
names input/output halves that arrived and were removed; absence of that marker
does not imply the exporter sent text.
Metadata and tags are developer labels, stored independently of the content
switches. Do not put end-user text in them. Supported sources include
tracelane.metadata.<key> / tracelane.tags, OpenInference metadata / tag.tags,
and Langfuse trace metadata/tags. Values are bounded and pass through ingest redaction.
Fields retained
The decoder maps supported OpenInferencellm.* aliases and current OTel GenAI
attributes into model, provider, token, finish-reason and tool metadata. Canonical
GenAI attributes win over aliases regardless of their order. Tool definitions
retain names and counts; schemas are not retained. Indexed OpenInference messages
are assembled in index order and then passed through the content decision.
Resource service.name, service.version and deployment.environment.name
(or legacy deployment.environment) reach each span; span attributes take
precedence. Default unknown-service names stay absent. Other resource attributes
are dropped.
Exception events retain type, message and a bounded stack trace as metadata.
Message events fold into the input/output fields and follow their capture setting.
Links retain trace/span IDs; link attributes are dropped. Supported MCP method,
session, protocol and tool metadata are retained. Ingest redaction applies to
retained attributes before storage.
Limits
These are the seeded defaults; operator policy can change them.
Oversized unknown strings are dropped, not truncated. Content and stack traces
are cut safely at UTF-8 boundaries; sufficiently large caps include
…[truncated]. Other batch, span-size and attribute-count limits still apply.
tracelane_attrs_dropped records dropped items by reason, including limits,
strings withheld by capture policy, unmapped content, resource keys and link attributes.
The gateway cache has a nominal 15-minute TTL; a failed refresh can retain the
last known choice longer. The direct ingest cache uses a 30-second TTL and drops
content when its policy lookup fails. Turning capture off affects new spans once
the receiving process observes the change. It does not retroactively erase
recorded text. See Prompt content
for ownership, redaction and retention details.