Why is data from only one Claude Code connector shown in reports?

If you see a notice on Claude Code reports that DX is showing data from one connector to avoid duplicates, your organization has both the Claude Code (OTel) connector and an API-based Claude Code connector — Claude Code (Enterprise) or Claude Code (Anthropic Console) — connected at the same time.

Why is this happening?

The OTel connector and the API-based connectors report the same underlying Claude Code usage through different channels. When both are connected, the same sessions, tokens, and spend are imported twice, which inflates usage and cost metrics.

To keep reporting accurate, DX shows only the API-based connector’s data and excludes Claude Code (OTel) data from reports. The notice on the report indicates this is in effect.

DX also prevents adding a Claude Code (OTel) connection when an API-based Claude Code connector already exists, and vice versa.

Which connector should I keep?

DX recommends using the API-based connector that matches your Anthropic billing plan and removing the redundant Claude Code (OTel) connection:

Keep the OTel connector only if your billing plan does not support an API-based connector.

Note: Both the Claude Code (Enterprise) and Claude Code (OTel) connectors provide per-model token usage and cost breakdowns. They differ in data source and dimensions: Enterprise data comes from Anthropic’s Analytics API, while OTel data comes from telemetry exported by Claude Code and can include OTel-specific dimensions such as terminal type. If your dashboards depend on connector-specific dimensions, contact your DX representative before removing a connection.

What happens to my data?

Excluding Claude Code (OTel) data is a reporting-level filter — no imported data is deleted while both connectors are connected.

If you have questions about removing a connection or about historical data, contact your DX representative or support@getdx.com.