# Open Telemetry (OTel) ## What is OTel? OTel is an open-source, vendor-neutral standard for generating, collecting, and exporting telemetry data such as metrics, logs, and traces. Multitudes uses OpenTelemetry to receive your AI tooling usage data. For more on OpenTelemetry, see the [official documentation](https://opentelemetry.io/docs/what-is-opentelemetry/?utm_source=chatgpt.com). ## How it works ### What metrics we can ingest and process We can ingest and process OTel data for the Claude Code [Team](https://claude.com/pricing/team) and [Individual](https://claude.com/pricing) plans, and Codex. If you're on the Claude Code [API](https://claude.com/pricing#api) or [Enterprise](https://claude.com/pricing/enterprise) plan, head to our docs here: [Claude Code](https://docs.multitudes.com/integrations/claude-code). {% hint style="info" %} If you'd like to bring in Open Telemetry data from other AI tools besides Claude Code or Codex, let us know at . {% endhint %} ### Integration options We can ingest OTel metrics in two different ways: #### 1. Multitudes-hosted collector Claude Code users send metrics directly to the Multitudes Open Telemetry collector running in Multitudes infrastructure. This avoids having to host a collector in your own infrastructure. To do this, follow steps below: [Multitudes-hosted collector](#multitudes-hosted-collector) #### 2. Self-hosted collector You run the Multitudes Open Telemetry collector in your infrastructure. The collector ingests metrics from Claude Code users and forwards them to Multitudes. To do this, follow the steps below: [Self-hosted collector](#self-hosted-collector) {% hint style="info" %} If you are already running an OTel collector and want to include Multitudes as another forwarding destination, reach out to us at . {% endhint %} ## Multitudes-hosted collector When using the Multitudes-hosted collector, each user sends their telemetry data directly to the Multitudes endpoint. For this, each user needs a configuration file that specifies the endpoint to use and an `Authorization` header. Apply the following configuration to each user's machine: #### For Claude: 1. Open the `~/.claude/settings.json` . 2. Add the following lines, using an API key that has been generated (following the instructions below): ```json "env": { "CLAUDE_CODE_ENABLE_TELEMETRY": "1", "OTEL_METRICS_EXPORTER": "otlp", "OTEL_LOGS_EXPORTER": "otlp", "OTEL_EXPORTER_OTLP_PROTOCOL": "http/protobuf", "OTEL_EXPORTER_OTLP_ENDPOINT": "https://integrations.multitudes.co/otel", "OTEL_METRIC_EXPORT_INTERVAL": "10000", "OTEL_EXPORTER_OTLP_HEADERS": "Authorization=Bearer " }, ``` {% hint style="info" %} The `Authorization` header can be an Organization API key if you are provisioning this file via MDM and want to use the same key across multiple users. If you would prefer that each user has their own key, they can create a Personal API key and update their `~/.claude/settings.json` file. {% endhint %} {% hint style="info" %} **AWS Bedrock:** when using Bedrock the `user.email` attribute must be configured manually via the `OTEL_RESOURCE_ATTRIBUTES` environment variable. This is because Bedrock authentication does not automatically provide user email information. Each user will need to add their work email address (or whichever email is associated with their user in Multitudes): ```json "env": { ... "OTEL_RESOURCE_ATTRIBUTES": "user.email=developer@company.com" } ``` {% endhint %} #### For Codex: 1. Open the `~/.codex/config.toml`. 2. Add the following lines: ```toml [otel] exporter = { otlp-http = { endpoint = "https://integrations.multitudes.co/otel/v1/logs", protocol = "binary", headers = { "Authorization" = "Bearer " } } } log_user_prompt = false ``` 3. Each user should generate a personal API key using the instructions below 4. Replace `` with your actual API key. Restart any sessions you might have in Claude. ## Self-hosted collector When using the self-hosted collector, each user sends their telemetry data to a collector run in your infrastrucutre, from which aggregated metrics are sent to Multitudes. ### Running the collector 1. Set up the Multitudes OTel Collector. Detailed instructions can be found [here](https://github.com/MultitudesCo/otel-collector). 2. Follow the instructions below to generate an Organization API key and run the collector using this key. ### Sending data to the collector Apply the following configuration to each user's machine: ```json { "env": { "CLAUDE_CODE_ENABLE_TELEMETRY": "1", "OTEL_METRICS_EXPORTER": "otlp", "OTEL_LOGS_EXPORTER": "otlp", "OTEL_EXPORTER_OTLP_PROTOCOL": "http/protobuf", "OTEL_EXPORTER_OTLP_ENDPOINT": "", "OTEL_METRIC_EXPORT_INTERVAL": "10000" } } ``` {% hint style="info" %} **AWS Bedrock:** when using Bedrock the `user.email` attribute must be configured manually via the `OTEL_RESOURCE_ATTRIBUTES` environment variable. This is because Bedrock authentication does not automatically provide user email information. Each user will need to add their work email address (or whichever email is associated with their user in Multitudes): ```json "env": { ... "OTEL_RESOURCE_ATTRIBUTES": "user.email=developer@company.com" } ``` {% endhint %} ## Checking data ingestion status Once you are sending data to Multitudes, either directly or via the self-hosted option, you can check the ingestion status in the Multitudes app, Open the [OpenTelemetry integration modal](https://app.multitudes.co/teamSettings/integrations?pill=true\&integration=otel) to check whether your data is coming through.
Once data is being received successfully, your Claude usage metrics will appear in Multitudes after our batch processing pipeline runs. Our pipeline runs daily, so in most cases you should expect to see metrics populate in the Multitudes App within up to one day of sending data. ## Generating an API Key {% hint style="info" %} All users can create personal API keys for sending OTel metrics directly to Multitudes. Owners can create organization API keys for running a central OTel collector that then forwards aggregated metrics to Multitudes {% endhint %} 1. From the [Settings > API Keys](https://app.multitudes.co/teamSettings/apiKeys) page, click "+ Generate New Key" on the top right corner of the page. This will pop-up a modal.
2. In the modal, select your key type. This depends on your organization setup. {% hint style="info" %} If you're running a self-hosted OTel collector or have only a single API key for everyone in the organization, then you can select the Organization key type. If you'd like team members to have separate API keys, then select Personal. {% endhint %} 3. Select "Write" for Open Telemetry. Once this is done, click "Create key".
4. After the key has been generated, copy it for use as the Bearer token in your OTel settings or when running your Multitudes OTel collector. The full key will only be shown once.
--- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.multitudes.com/integrations/open-telemetry.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.