[DOCS] Telemetry Configuration Ambiguity: Confusion between Anthropic internal metrics (Statsig) and User-managed OpenTelemetry

[coygeek]

Documentation Type

Missing documentation (feature not documented)

Documentation Location

• https://code.claude.com/docs/en/data-usage - https://code.claude.com/docs/en/monitoring-usage

Section/Topic

The configuration of "telemetry" across the "Data usage" and "Monitoring" sections.

Current Documentation

• On https://code.claude.com/docs/en/data-usage, under the "Telemetry services" section: "To opt out of Statsig telemetry, set the DISABLE_TELEMETRY environment variable."
• On https://code.claude.com/docs/en/monitoring-usage, under the "Quick start" section: "1. Enable telemetry: export CLAUDE_CODE_ENABLE_TELEMETRY=1"

What's Wrong or Missing?

The documentation uses the generic term "Telemetry" to refer to two entirely different systems without making a clear distinction:

1. Anthropic's internal operational telemetry (Statsig): An opt-out system used by Anthropic to track latency and reliability (configured via DISABLE_TELEMETRY).
2. User-managed OpenTelemetry (OTel): An opt-in feature allowing users to export metrics to their own OTLP collectors for monitoring (configured via CLAUDE_CODE_ENABLE_TELEMETRY).

Users may mistakenly believe that DISABLE_TELEMETRY disables all forms of metrics (including their own configured OTel stack) or that CLAUDE_CODE_ENABLE_TELEMETRY is required to "help improve Claude." This ambiguity is particularly significant for privacy-conscious enterprise users who need to distinguish between data leaving their network for Anthropic and data staying within their own observability infrastructure.

Suggested Improvement

The documentation should differentiate these features using more specific terminology.

• On https://code.claude.com/docs/en/monitoring-usage, rename the section to "User-Managed OpenTelemetry" or "Custom Observability."
• Update the Quick Start text on https://code.claude.com/docs/en/monitoring-usage to say: "1. Enable OpenTelemetry export: export CLAUDE_CODE_ENABLE_TELEMETRY=1"
• Add a clarifying note in both locations:

"Note: DISABLE_TELEMETRY applies to Anthropic's internal operational metrics (Statsig), whereas CLAUDE_CODE_ENABLE_TELEMETRY applies to your own OpenTelemetry collector configuration. These are independent systems."

Impact

High - Prevents users from using a feature

Additional Context

• Related documentation on environment variables: https://code.claude.com/docs/en/settings#environment-variables
• Many developers associate "Telemetry" strictly with "phoning home" to the developer, whereas "Monitoring" or "OpenTelemetry" is associated with their own dev-ops stack. Explicitly distinguishing the internal operational tracking from the OTel exporter would align with industry standard naming conventions (e.g., how VS Code distinguishes between "Telemetry" and "Breadcrumbs/Logs").

[github-actions]

Found 3 possible duplicate issues:

1. [FEATURE] Display telemetry notification and destination on startup #11057
2. [DOCS] OTEL_LOG_USER_PROMPTS missing from Environment Variables reference #18968
3. [DOCS] Clarify that OTEL telemetry exports events via logs protocol, not metrics #15417

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[coygeek]

Thank you for the updates to the documentation. I have reviewed the latest versions of the relevant pages against my original report regarding the ambiguity of the "Telemetry" terminology.

What’s FIXED

• Terminology Specificity in Data Usage: On https://code.claude.com/docs/en/data-usage, the section previously titled "Telemetry services" now specifically identifies the Statsig service and its purpose for operational metrics. The table at the bottom of that page also clearly labels the service as "Statsig (Metrics)" and correctly references the DISABLE_TELEMETRY variable.
• OpenTelemetry Identification: The page at https://code.claude.com/docs/en/monitoring-usage now includes a subtitle that explicitly mentions "OpenTelemetry (OTel) metrics and events," which helps contextualize the feature for developers.
• Environment Variable Descriptions: In the settings reference at https://code.claude.com/docs/en/settings#environment-variables, the entry for DISABLE_TELEMETRY now includes the clarifying parenthetical note that "Statsig events do not include user data like code, file paths, or bash commands."

What’s UNRESOLVED

• Lack of Explicit Independence Note: The original request for a clarifying note stating that DISABLE_TELEMETRY and CLAUDE_CODE_ENABLE_TELEMETRY are independent systems has not been implemented. This note is still needed on https://code.claude.com/docs/en/monitoring-usage and https://code.claude.com/docs/en/data-usage to prevent users from believing that disabling one affects the other.
• Generic "Quick Start" Text: The Quick Start section on https://code.claude.com/docs/en/monitoring-usage still uses the generic phrasing "1. Enable telemetry." For technical precision and to avoid confusion with Anthropic's internal tracking, this should be updated to "1. Enable OpenTelemetry export."
• Ambiguous Description in Settings Table: At https://code.claude.com/docs/en/settings#environment-variables, the description for CLAUDE_CODE_ENABLE_TELEMETRY is "Enables telemetry collection (required)." This remains misleading as it implies the telemetry is required for the application to function, rather than being the required toggle to enable the user's OTel exporter. It should be changed to "Enables OpenTelemetry (OTel) export."
• Page Title Ambiguity: The primary H1 title for https://code.claude.com/docs/en/monitoring-usage remains "Monitoring." While better than "Telemetry," it is still broad. Changing this to "User-Managed OpenTelemetry" would definitively resolve the conflict with the "Telemetry" section in the data usage documentation.

Conclusion

I am keeping this issue open. While the addition of "OpenTelemetry" in subtitles is a step in the right direction, the documentation still relies on the generic "Telemetry" label for two distinct data flows. This ambiguity remains a high-impact concern for enterprise users who must strictly audit where their data is being sent.

The primary requirement to resolve this issue is the inclusion of the "independent systems" note and the renaming of the "Enable telemetry" steps to "Enable OpenTelemetry export" to ensure clear distinction between Anthropic's operational tracking and the user's custom monitoring stack.

[github-actions]

Closing for now — inactive for too long. Please open a new issue if this is still relevant.

[github-actions]

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.