Send OTLP traces

Agent Registry accepts OTLP/HTTP protobuf traces, so runtimes without an atlanai SDK can export directly. Use it for Java, Ruby, Go, sidecars, and other OpenTelemetry runtimes. When a Python or TypeScript SDK is available, use it for typed observations and scores.

Before you begin

Before you start, make sure you have:

Credential: an API key and workspace ID from an approved secret store. Do not put headers in source code, container images, or deployment manifests.
Runtime: an OpenTelemetry SDK that exports OTLP/HTTP protobuf.

Set exporter environment

Set these variables from your secret store.

export ATLAN_BASE_URL="https://api.atlan.com"
export OTEL_EXPORTER_OTLP_TRACES_ENDPOINT="${ATLAN_BASE_URL}/otel/v1/traces"
export OTEL_EXPORTER_OTLP_PROTOCOL="http/protobuf"
export OTEL_EXPORTER_OTLP_HEADERS="Authorization=Bearer%20${ATLAN_API_KEY},X-Atlan-Workspace-Id=${ATLAN_WORKSPACE_ID}"

Run instrumented application

Start your application with its OpenTelemetry SDK enabled and send one request.

Verify trace

Open the trace in Agent Registry and confirm the root span, child spans, and parent relationships. See Send and verify traces for the full ingestion check.

Troubleshooting

If no trace appears, confirm the endpoint ends in /otel/v1/traces and that both the Authorization and X-Atlan-Workspace-Id headers are set. Install and setup errors covers failures inside atlanai SDK only.

Next steps

Send and verify traces: confirm ingestion and parent-child structure end to end.

Docs for AI agents

Before you begin

Troubleshooting

Next steps

See also

​Before you begin

​Troubleshooting

​Next steps

​See also

Before you begin

Troubleshooting

Next steps

See also