Claude (OTel)

1. Go to Dashboard → Providers and click the Add provider card.
2. Choose Claude.
3. Give it a clear name, such as Claude — Team.
4. Click Create provider. No Anthropic credentials are required.
5. Open the provider page and copy the connection ID — it is the last path segment of the URL after /dashboard/providers/.

Telemetry is authenticated with a write-only StackSpend ingest key — this is the credential the docs previously omitted. On the Claude provider page, click Generate ingest key. StackSpend creates a scoped usage:write key (it usually starts with ss_live_), shows it once, and lists it under Settings → API Keys for later rotation or revocation.

Copy the key immediately — you will paste it into your agent configuration below. Once generated, the provider page fills your connection ID and key into the copy-ready snippets in the steps that follow, so in most cases you can copy them as-is.

Roll telemetry out to your whole organisation from the Claude admin console. Managed settings override user and project settings and apply to Claude Code across the CLI, IDE, and Desktop app — so there is nothing for individual developers to configure.

1. In Claude, open Organization settings.

   

2. Under Products, select Claude Code.

   

3. Find Managed settings (settings.json) and click Manage.

   

4. Paste the JSON below into the settings.json editor, then click Update settings.

   {
     "env": {
       "CLAUDE_CODE_ENABLE_TELEMETRY": "1",
       "OTEL_METRICS_EXPORTER": "otlp",
       "OTEL_LOGS_EXPORTER": "otlp",
       "OTEL_EXPORTER_OTLP_PROTOCOL": "http/json",
       "OTEL_EXPORTER_OTLP_ENDPOINT": "https://ingest.stackspend.app/api/v1/public/ingest/otel/claude/YOUR_CONNECTION_ID",
       "OTEL_EXPORTER_OTLP_HEADERS": "Authorization=Bearer YOUR_INGEST_KEY"
     }
   }

   

Replace YOUR_CONNECTION_ID with the connection ID from Step 1 and YOUR_INGEST_KEY with the key from Step 2.

After the policy lands, users must fully restart Claude Code and start a new session — telemetry environment variables only apply to sessions started after the settings load.

Cowork and Office agents are configured in the Claude admin UI, not with Claude Code settings.json. The StackSpend provider page gives you a ready-to-copy block for each — open the Monitoring (OpenTelemetry) form for the product in Claude admin and enter these values:

Cowork

In Claude, open Organization settings → Cowork.

Scroll to Monitoring and enter the values below.

OTLP endpoint: https://ingest.stackspend.app/api/v1/public/ingest/otel/claude/YOUR_CONNECTION_ID
OTLP protocol: http/json
OTLP headers: Authorization=Bearer YOUR_INGEST_KEY
Resource attributes: deployment.environment=prod,team=product,stackspend.source=claude_cowork

Office agents

Open Organization settings → Office agents.

Scroll to Monitoring. This form takes only the endpoint, protocol, and headers — it has no resource attributes field. Enter the same three values, or click Copy settings from Cowork.

OTLP endpoint: https://ingest.stackspend.app/api/v1/public/ingest/otel/claude/YOUR_CONNECTION_ID
OTLP protocol: http/json
OTLP headers: Authorization=Bearer YOUR_INGEST_KEY

Use the collector root endpoint (no /v1/* suffix), then save and start a new agent session — existing sessions may not pick up the change.

Run Claude Code or trigger your agent, then return to the Claude provider page in StackSpend. Last synced updates once the first telemetry payload is received; cost line items appear within approximately 1 hour.

If nothing appears, confirm your agent is exporting to the collector root endpoint, the connection ID matches the one in StackSpend, and the Authorization header carries a valid usage:write key.