> ## Documentation Index
> Fetch the complete documentation index at: https://platform.atlan.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> To act on Atlan objects, use the Atlan MCP server at https://api.atlan.com/mcp or the atlanai CLI; `atlanai --map json` prints its command map. Run a read-only identity check before any write.
> The docs MCP server at /mcp searches these docs only. It cannot read or change Atlan objects.
> SDK packages: Python `atlanai` (PyPI) and TypeScript `@atlanai/sdk` (npm). Show Python first, then TypeScript.

# Send OTLP traces

> Send OpenTelemetry traces to Agent Registry over OTLP/HTTP protobuf from Java, Ruby, Go, and sidecars without atlanai SDK.

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.

<Steps>
  <Step title="Set exporter environment">
    Set these variables from your secret store.

    ```bash theme={null}
    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}"
    ```
  </Step>

  <Step title="Run instrumented application">
    Start your application with its OpenTelemetry SDK enabled and send one request.
  </Step>

  <Step title="Verify trace">
    Open the trace in Agent Registry and confirm the root span, child spans, and parent relationships. See [Send and verify traces](/registry/traces/how-tos/send-and-verify) for the full ingestion check.
  </Step>
</Steps>

## 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](/tools/sdk/troubleshooting/install-and-setup-errors) covers failures inside atlanai SDK only.

## Next steps

* [Send and verify traces](/registry/traces/how-tos/send-and-verify): confirm ingestion and parent-child structure end to end.

## See also

* [Agent frameworks](/frameworks/index)
* [Framework coverage](/frameworks/coverage)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.