Telemetry
Usage telemetry configuration for Claude Code is documented in the Claude Code setup guide.
Overview
Telemetry enables PwC to track ROI, analyze usage patterns, and understand how AI coding assistants are being used across the organization. This data is essential for continued investment in these tools.
Metrics Collected
The following metrics are collected and sent to the PwC OTEL Collector:
| Metric | Description |
|---|---|
claude_code.session.count | Number of Claude Code sessions |
claude_code.lines_of_code.count | Lines of code generated or modified |
claude_code.commit.count | Number of git commits made during sessions |
claude_code.cost.usage | Session cost in dollars |
claude_code.token.usage | Token consumption (input and output) |
These metrics help teams understand:
- How frequently Claude Code is being used
- The volume of code being generated
- Cost efficiency and ROI
- Usage trends over time
Privacy Considerations
The telemetry system collects only:
- Aggregate usage metrics (session counts, token usage, costs)
- Code volume metrics (lines changed, commits made)
- Department and team identifiers you provide
The telemetry does not collect:
- Actual code content
- Conversation content
- Personal identifiable information beyond team assignment
- File names or project details
Troubleshooting
Telemetry Not Being Sent
-
Check
OTEL_EXPORTER_OTLP_HEADERS- This is the most common issue. Ensure this variable is set with the correct authorization header format:authorization=Bearer apikey=<key>&tenantid=<id> -
Verify
CLAUDE_CODE_ENABLE_TELEMETRYis set to1 -
Ensure VPN connection - You must be connected to the PwC network (Italy VPN) to reach the OTEL collector endpoint
-
Verify endpoint reachability:
curl -I https://idi-coding-agents.pwc.it/health
Settings Not Loaded
-
Check if
~/.claude/settings.jsonexists:ls -la ~/.claude/settings.json -
Verify the JSON syntax is valid:
jq . ~/.claude/settings.json -
Restart Claude Code after making changes to
settings.json