Monitoring

Documentation Index

Fetch the complete documentation index at: https://code.claude.com/docs/llms.txt

Use this file to discover all available pages before exploring further.

​

Quick start

# 1. Enable telemetry
export CLAUDE_CODE_ENABLE_TELEMETRY=1

# 2. Choose exporters (both are optional - configure only what you need)
export OTEL_METRICS_EXPORTER=otlp       # Options: otlp, prometheus, console, none
export OTEL_LOGS_EXPORTER=otlp          # Options: otlp, console, none

# 3. Configure OTLP endpoint (for OTLP exporter)
export OTEL_EXPORTER_OTLP_PROTOCOL=grpc
export OTEL_EXPORTER_OTLP_ENDPOINT=http://localhost:4317

# 4. Set authentication (if required)
export OTEL_EXPORTER_OTLP_HEADERS="Authorization=Bearer your-token"

# 5. For debugging: reduce export intervals
export OTEL_METRIC_EXPORT_INTERVAL=10000  # 10 seconds (default: 60000ms)
export OTEL_LOGS_EXPORT_INTERVAL=5000     # 5 seconds (default: 5000ms)

# 6. Run Claude Code
claude

​

Administrator configuration

{
  "env": {
    "CLAUDE_CODE_ENABLE_TELEMETRY": "1",
    "OTEL_METRICS_EXPORTER": "otlp",
    "OTEL_LOGS_EXPORTER": "otlp",
    "OTEL_EXPORTER_OTLP_PROTOCOL": "grpc",
    "OTEL_EXPORTER_OTLP_ENDPOINT": "http://collector.example.com:4317",
    "OTEL_EXPORTER_OTLP_HEADERS": "Authorization=Bearer example-token"
  }
}

​

Configuration details

​

Common configuration variables

​

mTLS authentication

​

Metrics cardinality control

​

Traces (beta)

​

Span hierarchy

claude_code.interaction
├── claude_code.llm_request
├── claude_code.hook                    (requires detailed beta tracing)
└── claude_code.tool
    ├── claude_code.tool.blocked_on_user
    ├── claude_code.tool.execution
    └── (Task tool) subagent claude_code.llm_request / claude_code.tool spans

​

Span attributes

​

Dynamic headers

​

Settings configuration

{
  "otelHeadersHelper": "/bin/generate_opentelemetry_headers.sh"
}

​

Script requirements

#!/bin/bash
# Example: Multiple headers
echo "{\"Authorization\": \"Bearer $(get-token.sh)\", \"X-API-Key\": \"$(get-api-key.sh)\"}"

​

Refresh behavior

​

Multi-team organization support

# Add custom attributes for team identification
export OTEL_RESOURCE_ATTRIBUTES="department=engineering,team.id=platform,cost_center=eng-123"

• Filter metrics by team or department
• Track costs per cost center
• Create team-specific dashboards
• Set up alerts for specific teams

# ❌ Invalid - contains spaces
export OTEL_RESOURCE_ATTRIBUTES="org.name=John's Organization"

# ✅ Valid - use underscores or camelCase instead
export OTEL_RESOURCE_ATTRIBUTES="org.name=Johns_Organization"
export OTEL_RESOURCE_ATTRIBUTES="org.name=JohnsOrganization"

# ✅ Valid - percent-encode special characters if needed
export OTEL_RESOURCE_ATTRIBUTES="org.name=John%27s%20Organization"

​

Example configurations

# Console debugging (1-second intervals)
export CLAUDE_CODE_ENABLE_TELEMETRY=1
export OTEL_METRICS_EXPORTER=console
export OTEL_METRIC_EXPORT_INTERVAL=1000

# OTLP/gRPC
export CLAUDE_CODE_ENABLE_TELEMETRY=1
export OTEL_METRICS_EXPORTER=otlp
export OTEL_EXPORTER_OTLP_PROTOCOL=grpc
export OTEL_EXPORTER_OTLP_ENDPOINT=http://localhost:4317

# Prometheus
export CLAUDE_CODE_ENABLE_TELEMETRY=1
export OTEL_METRICS_EXPORTER=prometheus

# Multiple exporters
export CLAUDE_CODE_ENABLE_TELEMETRY=1
export OTEL_METRICS_EXPORTER=console,otlp
export OTEL_EXPORTER_OTLP_PROTOCOL=http/json

# Different endpoints/backends for metrics and logs
export CLAUDE_CODE_ENABLE_TELEMETRY=1
export OTEL_METRICS_EXPORTER=otlp
export OTEL_LOGS_EXPORTER=otlp
export OTEL_EXPORTER_OTLP_METRICS_PROTOCOL=http/protobuf
export OTEL_EXPORTER_OTLP_METRICS_ENDPOINT=http://metrics.example.com:4318
export OTEL_EXPORTER_OTLP_LOGS_PROTOCOL=grpc
export OTEL_EXPORTER_OTLP_LOGS_ENDPOINT=http://logs.example.com:4317

# Metrics only (no events/logs)
export CLAUDE_CODE_ENABLE_TELEMETRY=1
export OTEL_METRICS_EXPORTER=otlp
export OTEL_EXPORTER_OTLP_PROTOCOL=grpc
export OTEL_EXPORTER_OTLP_ENDPOINT=http://localhost:4317

# Events/logs only (no metrics)
export CLAUDE_CODE_ENABLE_TELEMETRY=1
export OTEL_LOGS_EXPORTER=otlp
export OTEL_EXPORTER_OTLP_PROTOCOL=grpc
export OTEL_EXPORTER_OTLP_ENDPOINT=http://localhost:4317

​

Available metrics and events

​

Standard attributes

• prompt.id: UUID correlating a user prompt with all subsequent events until the next prompt. See Event correlation attributes.
• workspace.host_paths: host workspace directories selected in the desktop app, as a string array

​

Metrics

​

Metric details

​

Session counter

• All standard attributes
• start_type: How the session was started. One of "fresh", "resume", or "continue"

​

Lines of code counter

• All standard attributes
• type: ("added", "removed")

​

Pull request counter

• All standard attributes

​

Commit counter

• All standard attributes

​

Cost counter

• All standard attributes
• model: Model identifier (for example, “claude-sonnet-4-6”)
• query_source: Category of the subsystem that issued the request. One of "main", "subagent", or "auxiliary"
• speed: "fast" when the request used fast mode. Absent otherwise
• effort: Effort level applied to the request: "low", "medium", "high", "xhigh", or "max". Absent when the model does not support effort.
• agent.name: Subagent type that issued the request. Built-in agent names and agents from official-marketplace plugins appear verbatim. Other user-defined agent names are replaced with "custom". Absent when the request was not issued by a named subagent type.
• skill.name: Skill active for the request, set by the Skill tool, a / command, or inherited by a spawned subagent. Built-in, bundled, user-defined, and official-marketplace plugin skill names appear verbatim. Third-party plugin skill names are replaced with "third-party". Absent when no skill is active.
• plugin.name: Owning plugin when the active skill or subagent is provided by a plugin. Official-marketplace plugin names appear verbatim. Third-party plugin names are replaced with "third-party". Absent when neither the skill nor the subagent has an owning plugin.
• marketplace.name: Marketplace the owning plugin was installed from. Only emitted for official-marketplace plugins. Absent otherwise.

​

Token counter

• All standard attributes
• type: ("input", "output", "cacheRead", "cacheCreation")
• model: Model identifier (for example, “claude-sonnet-4-6”)
• query_source: Category of the subsystem that issued the request. One of "main", "subagent", or "auxiliary"
• speed: "fast" when the request used fast mode. Absent otherwise
• effort: Effort level applied to the request. See Cost counter for details.
• agent.name, skill.name, plugin.name, marketplace.name: Skill, plugin, and agent attribution for the request. See Cost counter for definitions and redaction behavior.

​

Code edit tool decision counter

• All standard attributes
• tool_name: Tool name ("Edit", "Write", "NotebookEdit")
• decision: User decision ("accept", "reject")
• source: Where the decision came from. One of "config", "hook", "user_permanent", "user_temporary", "user_abort", or "user_reject". See the Tool decision event for what each value means.
• language: Programming language of the edited file, such as "TypeScript", "Python", "JavaScript", or "Markdown". Returns "unknown" for unrecognized file extensions.

​

Active time counter

• All standard attributes
• type: "user" for keyboard interactions, "cli" for tool execution and AI responses

​

Events

​

Event correlation attributes

​

User prompt event

• All standard attributes
• event.name: "user_prompt"
• event.timestamp: ISO 8601 timestamp
• event.sequence: monotonically increasing counter for ordering events within a session
• prompt_length: Length of the prompt
• prompt: Prompt content (redacted by default, enable with OTEL_LOG_USER_PROMPTS=1)
• command_name: Command name when the prompt invokes one. Built-in and bundled command names such as compact or debug are emitted as-is; aliases such as reset emit as typed rather than the canonical name. Custom, plugin, and MCP command names collapse to custom or mcp unless OTEL_LOG_TOOL_DETAILS=1 is set
• command_source: Origin of the command when present: builtin, custom, or mcp. Plugin-provided commands report as custom

​

Tool result event

• All standard attributes
• event.name: "tool_result"
• event.timestamp: ISO 8601 timestamp
• event.sequence: monotonically increasing counter for ordering events within a session
• tool_name: Name of the tool
• tool_use_id: Unique identifier for this tool invocation. Matches the tool_use_id passed to hooks, allowing correlation between OTel events and hook-captured data.
• success: "true" or "false"
• duration_ms: Execution time in milliseconds
• error_type: Error category string when the tool failed, such as "Error:ENOENT" or "ShellError"
• error (when OTEL_LOG_TOOL_DETAILS=1): Full error message when the tool failed
• decision_type: Either "accept" or "reject"
• decision_source: Where the decision came from. One of "config", "hook", "user_permanent", "user_temporary", "user_abort", or "user_reject". See the Tool decision event for what each value means.
• tool_input_size_bytes: Size of the JSON-serialized tool input in bytes
• tool_result_size_bytes: Size of the tool result in bytes
• mcp_server_scope: MCP server scope identifier (for MCP tools)
• tool_parameters (when OTEL_LOG_TOOL_DETAILS=1): JSON string containing tool-specific parameters:
  • For Bash tool: includes bash_command, full_command, timeout, description, dangerouslyDisableSandbox, and git_commit_id (the commit SHA, when a git commit command succeeds)
  • For MCP tools: includes mcp_server_name, mcp_tool_name
  • For Skill tool: includes skill_name
  • For Task tool: includes subagent_type
• tool_input (when OTEL_LOG_TOOL_DETAILS=1): JSON-serialized tool arguments. Individual values over 512 characters are truncated, and the full payload is bounded to ~4 K characters. Applies to all tools including MCP tools.

​

API request event

• All standard attributes
• event.name: "api_request"
• event.timestamp: ISO 8601 timestamp
• event.sequence: monotonically increasing counter for ordering events within a session
• model: Model used (for example, “claude-sonnet-4-6”)
• cost_usd: Estimated cost in USD
• duration_ms: Request duration in milliseconds
• input_tokens: Number of input tokens
• output_tokens: Number of output tokens
• cache_read_tokens: Number of tokens read from cache
• cache_creation_tokens: Number of tokens used for cache creation
• request_id: Anthropic API request ID from the response’s request-id header, such as "req_011...". Present only when the API returns one.
• speed: "fast" or "normal", indicating whether fast mode was active
• query_source: Subsystem that issued the request, such as "repl_main_thread", "compact", or a subagent name
• effort: Effort level applied to the request: "low", "medium", "high", "xhigh", or "max". Absent when the model does not support effort.

​

API error event

• All standard attributes
• event.name: "api_error"
• event.timestamp: ISO 8601 timestamp
• event.sequence: monotonically increasing counter for ordering events within a session
• model: Model used (for example, “claude-sonnet-4-6”)
• error: Error message
• status_code: HTTP status code as a number. Absent for non-HTTP errors such as connection failures.
• duration_ms: Request duration in milliseconds
• attempt: Total number of attempts made, including the initial request (1 means no retries occurred)
• request_id: Anthropic API request ID from the response’s request-id header, such as "req_011...". Present only when the API returns one.
• speed: "fast" or "normal", indicating whether fast mode was active
• query_source: Subsystem that issued the request, such as "repl_main_thread", "compact", or a subagent name
• effort: Effort level applied to the request. Absent when the model does not support effort.

​

API request body event

• All standard attributes
• event.name: "api_request_body"
• event.timestamp: ISO 8601 timestamp
• event.sequence: monotonically increasing counter for ordering events within a session
• body: JSON-serialized Messages API request parameters (system prompt, messages, tools, etc.), truncated at 60 KB. Extended-thinking content in prior assistant turns is redacted. Emitted only in inline mode (OTEL_LOG_RAW_API_BODIES=1).
• body_ref: Absolute path to a <dir>/<uuid>.request.json file containing the untruncated body. Emitted only in file mode (OTEL_LOG_RAW_API_BODIES=file:<dir>).
• body_length: Untruncated body length. UTF-8 bytes when OTEL_LOG_RAW_API_BODIES=file:<dir>, or UTF-16 code units when =1
• body_truncated: "true" when inline truncation occurred. Absent in file mode and when no truncation occurred.
• model: Model identifier from the request parameters
• query_source: Subsystem that issued the request (for example, "compact")

​

API response body event

• All standard attributes
• event.name: "api_response_body"
• event.timestamp: ISO 8601 timestamp
• event.sequence: monotonically increasing counter for ordering events within a session
• body: JSON-serialized Messages API response (id, content blocks, usage, stop reason), truncated at 60 KB. Extended-thinking content is redacted. Emitted only in inline mode (OTEL_LOG_RAW_API_BODIES=1).
• body_ref: Absolute path to a <dir>/<request_id>.response.json file containing the untruncated body. Emitted only in file mode (OTEL_LOG_RAW_API_BODIES=file:<dir>).
• body_length: Untruncated body length. UTF-8 bytes when OTEL_LOG_RAW_API_BODIES=file:<dir>, or UTF-16 code units when =1
• body_truncated: "true" when inline truncation occurred. Absent in file mode and when no truncation occurred.
• model: Model identifier
• query_source: Subsystem that issued the request
• request_id: Anthropic API request ID from the response’s request-id header, such as "req_011...". Present only when the API returns one.

​

Tool decision event

• All standard attributes
• event.name: "tool_decision"
• event.timestamp: ISO 8601 timestamp
• event.sequence: monotonically increasing counter for ordering events within a session
• tool_name: Name of the tool (for example, “Read”, “Edit”, “Write”, “NotebookEdit”)
• tool_use_id: Unique identifier for this tool invocation. Matches the tool_use_id passed to hooks, allowing correlation between OTel events and hook-captured data.
• decision: Either "accept" or "reject"
• source: Where the decision came from:
  • "config": Decided automatically without prompting, based on project settings, allow rules in the user’s personal settings, enterprise managed policy, --allowedTools or --disallowedTools flags, the active permission mode, a session-scoped grant from an earlier prompt in the same interactive CLI session, or because the tool is inherently safe. The event does not indicate which of these sources matched.
  • "hook": A PreToolUse or PermissionRequest hook returned the decision.
  • "user_permanent": Emitted when the user chose “Yes, and don’t ask again for …” at a permission prompt, which saves an allow rule to their personal settings. In the interactive CLI this is emitted only for that choice itself; later calls that match the saved rule emit "config" instead. In Agent SDK or non-interactive -p sessions, both the initial choice and later rule matches emit "user_permanent". Treated as an accept.
  • "user_temporary": Emitted when the user chose “Yes” at a permission prompt for a one-time approval, or chose one of the ”… during this session” options on a file edit or read prompt. In the interactive CLI this is emitted only for the choice itself; later calls allowed by that session-scoped grant emit "config" instead. In Agent SDK or non-interactive -p sessions, both the choice and later matches emit "user_temporary". Treated as an accept.
  • "user_abort": Emitted when the user dismissed the permission prompt without answering. Treated as a reject.
  • "user_reject": Emitted when the user chose “No” when prompted, or a call matched a deny rule in their personal settings. Treated as a reject.

​

Permission mode changed event

• All standard attributes
• event.name: "permission_mode_changed"
• event.timestamp: ISO 8601 timestamp
• event.sequence: monotonically increasing counter for ordering events within a session
• from_mode: The previous permission mode, for example "default", "plan", "acceptEdits", "auto", or "bypassPermissions"
• to_mode: The new permission mode
• trigger: What caused the change. One of "shift_tab", "exit_plan_mode", "auto_gate_denied", or "auto_opt_in". Absent when the transition originates from the SDK or bridge

​

Auth event

• All standard attributes
• event.name: "auth"
• event.timestamp: ISO 8601 timestamp
• event.sequence: monotonically increasing counter for ordering events within a session
• action: "login" or "logout"
• success: "true" or "false"
• auth_method: Authentication method, such as "oauth"
• error_category: Categorical error kind when the action failed. The raw error message is never included
• status_code: HTTP status code as a string when the action failed with an HTTP error

​

MCP server connection event

• All standard attributes
• event.name: "mcp_server_connection"
• event.timestamp: ISO 8601 timestamp
• event.sequence: monotonically increasing counter for ordering events within a session
• status: "connected", "failed", or "disconnected"
• transport_type: Server transport, such as "stdio", "sse", or "http"
• server_scope: Scope the server is configured at, such as "user", "project", or "local"
• duration_ms: Connection attempt duration in milliseconds
• error_code: Error code when the connection failed
• server_name (when OTEL_LOG_TOOL_DETAILS=1): Configured server name
• error (when OTEL_LOG_TOOL_DETAILS=1): Full error message when the connection failed

​

Internal error event

• All standard attributes
• event.name: "internal_error"
• event.timestamp: ISO 8601 timestamp
• event.sequence: monotonically increasing counter for ordering events within a session
• error_name: Error class name, such as "TypeError" or "SyntaxError"
• error_code: Node.js errno code such as "ENOENT" when present on the error

​

Plugin installed event

• All standard attributes
• event.name: "plugin_installed"
• event.timestamp: ISO 8601 timestamp
• event.sequence: monotonically increasing counter for ordering events within a session
• marketplace.is_official: "true" if the marketplace is an official Anthropic marketplace, "false" otherwise
• install.trigger: "cli" or "ui"
• plugin.name: Name of the installed plugin. For third-party marketplaces this is included only when OTEL_LOG_TOOL_DETAILS=1
• plugin.version: Plugin version when declared in the marketplace entry. For third-party marketplaces this is included only when OTEL_LOG_TOOL_DETAILS=1
• marketplace.name: Marketplace the plugin was installed from. For third-party marketplaces this is included only when OTEL_LOG_TOOL_DETAILS=1

​

Plugin loaded event

• All standard attributes
• event.name: "plugin_loaded"
• event.timestamp: ISO 8601 timestamp
• event.sequence: monotonically increasing counter for ordering events within a session
• plugin.name: name of the plugin. For plugins outside the official marketplace and built-in bundle the value is "third-party" unless OTEL_LOG_TOOL_DETAILS=1
• marketplace.name: marketplace the plugin was installed from, when known. Redacted to "third-party" under the same condition as plugin.name
• plugin.version: version from the plugin manifest. Included only when the name is not redacted and the manifest declares a version
• plugin.scope: provenance category for the plugin: "official", "org", "user-local", or "default-bundle"
• enabled_via: how the plugin came to be enabled: "default-enable", "org-policy", "seed-mount", or "user-install"
• plugin_id_hash: deterministic hash of the plugin name and marketplace, sent only to your configured exporter. Lets you count how many distinct third-party plugins are loaded across your fleet without recording their names
• has_hooks: whether the plugin contributes hooks
• has_mcp: whether the plugin contributes MCP servers
• skill_path_count: number of skill directories the plugin declares
• command_path_count: number of command directories the plugin declares
• agent_path_count: number of agent directories the plugin declares

​

Skill activated event

• All standard attributes
• event.name: "skill_activated"
• event.timestamp: ISO 8601 timestamp
• event.sequence: monotonically increasing counter for ordering events within a session
• skill.name: Name of the skill. For user-defined and third-party plugin skills the value is the placeholder "custom_skill" unless OTEL_LOG_TOOL_DETAILS=1
• invocation_trigger: How the skill was triggered ("user-slash", "claude-proactive", or "nested-skill")
• skill.source: Where the skill was loaded from (for example, "bundled", "userSettings", "projectSettings", "plugin")
• plugin.name (when OTEL_LOG_TOOL_DETAILS=1 or the plugin is from an official marketplace): Name of the owning plugin when the skill is provided by a plugin
• marketplace.name (when OTEL_LOG_TOOL_DETAILS=1 or the plugin is from an official marketplace): Marketplace the owning plugin was installed from, when the skill is provided by a plugin

​

At mention event

• All standard attributes
• event.name: "at_mention"
• event.timestamp: ISO 8601 timestamp
• event.sequence: monotonically increasing counter for ordering events within a session
• mention_type: Type of mention ("file", "directory", "agent", "mcp_resource")
• success: Whether the mention resolved successfully ("true" or "false")

​

API retries exhausted event

• All standard attributes
• event.name: "api_retries_exhausted"
• event.timestamp: ISO 8601 timestamp
• event.sequence: monotonically increasing counter for ordering events within a session
• model: Model used
• error: Final error message
• status_code: HTTP status code as a number. Absent for non-HTTP errors.
• total_attempts: Total number of attempts made
• total_retry_duration_ms: Total wall-clock time across all attempts
• speed: "fast" or "normal"

​

Hook registered event

• All standard attributes
• event.name: "hook_registered"
• event.timestamp: ISO 8601 timestamp
• event.sequence: monotonically increasing counter for ordering events within a session
• hook_event: hook event type, such as "PreToolUse" or "PostToolUse"
• hook_type: hook implementation type: "command", "prompt", "mcp_tool", "http", or "agent"
• hook_source: where the hook is defined: "userSettings", "projectSettings", "localSettings", "flagSettings", "policySettings", or "pluginHook"
• hook_matcher (when OTEL_LOG_TOOL_DETAILS=1): the matcher string from the hook configuration, when one is set
• plugin.name (when hook_source is "pluginHook"): name of the contributing plugin. For plugins outside the official marketplace and built-in bundle the value is "third-party" unless OTEL_LOG_TOOL_DETAILS=1
• plugin_id_hash (when hook_source is "pluginHook"): deterministic hash of the plugin name and marketplace, sent only to your configured exporter. Lets you count distinct contributing plugins without recording their names

​

Hook execution start event

• All standard attributes
• event.name: "hook_execution_start"
• event.timestamp: ISO 8601 timestamp
• event.sequence: monotonically increasing counter for ordering events within a session
• hook_event: Hook event type, such as "PreToolUse" or "PostToolUse"
• hook_name: Full hook name including matcher, such as "PreToolUse:Write"
• num_hooks: Number of matching hook commands
• managed_only: "true" when only managed-policy hooks are permitted
• hook_source: "policySettings" or "merged"
• hook_definitions: JSON-serialized hook configuration. Included only when both detailed beta tracing and OTEL_LOG_TOOL_DETAILS=1 are enabled

​

Hook execution complete event

• All standard attributes
• event.name: "hook_execution_complete"
• event.timestamp: ISO 8601 timestamp
• event.sequence: monotonically increasing counter for ordering events within a session
• hook_event: Hook event type
• hook_name: Full hook name including matcher
• num_hooks: Number of matching hook commands
• num_success: Count that completed successfully
• num_blocking: Count that returned a blocking decision
• num_non_blocking_error: Count that failed without blocking
• num_cancelled: Count cancelled before completion
• total_duration_ms: Wall-clock duration of all matching hooks
• managed_only: "true" when only managed-policy hooks are permitted
• hook_source: "policySettings" or "merged"
• hook_definitions: JSON-serialized hook configuration. Included only when both detailed beta tracing and OTEL_LOG_TOOL_DETAILS=1 are enabled

​

Compaction event

• All standard attributes
• event.name: "compaction"
• event.timestamp: ISO 8601 timestamp
• event.sequence: monotonically increasing counter for ordering events within a session
• trigger: "auto" or "manual"
• success: "true" or "false"
• duration_ms: Compaction duration
• pre_tokens: Approximate token count before compaction
• post_tokens: Approximate token count after compaction
• error: Error message when compaction failed

​

Feedback survey event

• All standard attributes
• event.name: "feedback_survey"
• event.timestamp: ISO 8601 timestamp
• event.sequence: monotonically increasing counter for ordering events within a session
• event_type: Survey lifecycle event, for example "appeared", "responded", or "transcript_prompt_appeared"
• appearance_id: Unique ID linking the events emitted for one survey instance
• survey_type: Which survey produced the event. "session" is the “How is Claude doing?” rating prompt
• response: The user’s selection on responded events
• enabled_via_override: true when CLAUDE_CODE_ENABLE_FEEDBACK_SURVEY_FOR_OTEL is set. Emitted as a boolean, not a string. Present on session survey events. Filter on this attribute to confirm the override is applied across a fleet

​

Interpret metrics and events data

​

Usage monitoring

​

Cost monitoring

• Tracking usage trends across teams or individuals
• Identifying high-usage sessions for optimization
• Attributing spend to specific skills, plugins, or subagent types via the skill.name, plugin.name, and agent.name attributes

​

Alerting and segmentation

• Cost spikes
• Unusual token consumption
• High session volume from specific users

​

Detect retry exhaustion

​

Event analysis

• Most frequently used tools
• Tool success rates
• Average tool execution times
• Error patterns by tool type

​

Audit security events

​

Attribute actions to users

export OTEL_RESOURCE_ATTRIBUTES="enduser.id=jdoe@example.com,enduser.directory_id=S-1-5-21-..."

​

Audit MCP activity

​

Map security questions to events

​

Send events to a SIEM

{
  "env": {
    "CLAUDE_CODE_ENABLE_TELEMETRY": "1",
    "OTEL_LOGS_EXPORTER": "otlp",
    "OTEL_LOG_TOOL_DETAILS": "1",
    "OTEL_EXPORTER_OTLP_LOGS_PROTOCOL": "http/protobuf",
    "OTEL_EXPORTER_OTLP_LOGS_ENDPOINT": "https://siem.example.com:4318/v1/logs",
    "OTEL_EXPORTER_OTLP_HEADERS": "Authorization=Bearer your-siem-token"
  }
}

​

Backend considerations

​

For metrics

• Time series databases (for example, Prometheus): Rate calculations, aggregated metrics
• Columnar stores (for example, ClickHouse): Complex queries, unique user analysis
• Full-featured observability platforms (for example, Honeycomb, Datadog): Advanced querying, visualization, alerting

​

For events/logs

• Log aggregation systems (for example, Elasticsearch, Loki): Full-text search, log analysis
• Columnar stores (for example, ClickHouse): Structured event analysis
• Full-featured observability platforms (for example, Honeycomb, Datadog): Correlation between metrics and events

​

For traces

• Distributed tracing systems (for example, Jaeger, Zipkin, Grafana Tempo): Span visualization, request waterfalls, latency analysis
• Full-featured observability platforms (for example, Honeycomb, Datadog): Trace search and correlation with metrics and logs

​

Service information

• service.name: claude-code
• service.version: Current Claude Code version
• os.type: Operating system type (for example, linux, darwin, windows)
• os.version: Operating system version string
• host.arch: Host architecture (for example, amd64, arm64)
• wsl.version: WSL version number (only present when running on Windows Subsystem for Linux)
• Meter Name: com.anthropic.claude_code

​

ROI measurement resources

​

Security and privacy

• OpenTelemetry export to your backend is opt-in and requires explicit configuration. For Anthropic’s separate operational telemetry and how to disable it, see Data usage
• Raw file contents and code snippets are not included in metrics or events. Trace spans are a separate data path: see the OTEL_LOG_TOOL_CONTENT bullet below
• When authenticated via OAuth, user.email is included in telemetry attributes. If this is a concern for your organization, work with your telemetry backend to filter or redact this field
• User prompt content is not collected by default. Only prompt length is recorded. To include prompt content, set OTEL_LOG_USER_PROMPTS=1
• Tool input arguments and parameters are not logged by default. To include them, set OTEL_LOG_TOOL_DETAILS=1. When enabled, tool_result events include a tool_parameters attribute with Bash commands, MCP server and tool names, and skill names, plus a tool_input attribute with file paths, URLs, search patterns, and other arguments. user_prompt events include the verbatim command_name for custom, plugin, and MCP commands. Trace spans include the same tool_input attribute and input-derived attributes such as file_path. Individual values over 512 characters are truncated and the total is bounded to ~4 K characters, but the arguments may still contain sensitive values. Configure your telemetry backend to filter or redact these attributes as needed
• Tool input and output content is not logged in trace spans by default. To include it, set OTEL_LOG_TOOL_CONTENT=1. When enabled, span events include full tool input and output content truncated at 60 KB per span. This can include raw file contents from Read tool results and Bash command output. Configure your telemetry backend to filter or redact these attributes as needed
• Raw Anthropic Messages API request and response bodies are not logged by default. To include them, set OTEL_LOG_RAW_API_BODIES. With =1, each API call emits api_request_body and api_response_body log events whose body attribute is the JSON-serialized payload, truncated at 60 KB. With =file:<dir>, untruncated bodies are written to .request.json and .response.json files under that directory and the events carry a body_ref path instead of the inline body. Ship the directory with a log collector or sidecar rather than through the telemetry stream. In both modes, bodies contain the full conversation history (system prompt, every prior user and assistant turn, tool results), so enabling this implies consent to everything the other OTEL_LOG_* content flags would reveal. Claude’s extended-thinking content is always redacted from these bodies regardless of other settings

​

Monitor Claude Code on Amazon Bedrock