# Monitoring - Anthropic

Source: https://docs.anthropic.com/en/docs/claude-code/monitoring-usage
Last Updated: 2025-06-24T09:05:48.840649

---

Anthropic home page English Search... Search... Navigation Administration Monitoring Welcome Developer Guide API Guide Claude Code Model Context Protocol (MCP) Resources Release Notes Documentation Developer Discord Support Getting started Overview Set up Quickstart Memory management Common workflows Build with Claude Add Claude Code to your IDE Model Context Protocol (MCP) GitHub Actions Claude Code SDK Troubleshooting Deployment Overview Amazon Bedrock Google Vertex AI Corporate proxy LLM gateway Development containers Administration Identity and Access Management Security Monitoring Costs Reference CLI reference Interactive mode Slash commands Settings Resources Data usage Legal and compliance Claude Code supports OpenTelemetry (OTel) metrics and events for monitoring and observability. All metrics are time series data exported via OpenTelemetrys standard metrics protocol, and events are exported via OpenTelemetrys logs/events protocol. It is the users responsibility to ensure their metrics and logs backends are properly configured and that the aggregation granularity meets their monitoring requirements. OpenTelemetry support is currently in beta and details are subject to change.  Quick Start Configure OpenTelemetry using environment variables: export CLAUDE_CODE_ENABLE_TELEMETRY = 1 export OTEL_METRICS_EXPORTER = otlp export OTEL_LOGS_EXPORTER = otlp export OTEL_EXPORTER_OTLP_PROTOCOL = grpc export OTEL_EXPORTER_OTLP_ENDPOINT = http://localhost:4317 export OTEL_EXPORTER_OTLP_HEADERS = "Authorization=Bearer your-token" export OTEL_METRIC_EXPORT_INTERVAL = 10000 export OTEL_LOGS_EXPORT_INTERVAL = 5000 claude The default export intervals are 60 seconds for metrics and 5 seconds for logs. During setup, you may want to use shorter intervals for debugging purposes. Remember to reset these for production use. For full configuration options, see the OpenTelemetry specification .  Administrator Configuration Administrators can configure OpenTelemetry settings for all users through the managed settings file. This allows for centralized control of telemetry settings across an organization. See the settings precedence for more information about how settings are applied. The managed settings file is located at: macOS: /Library/Application Support/ClaudeCode/managed-settings.json Linux: /etc/claude-code/managed-settings.json Example managed settings 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.company.com:4317" , "OTEL_EXPORTER_OTLP_HEADERS" : "Authorization=Bearer company-token" } } Managed settings can be distributed via MDM (Mobile Device Management) or other device management solutions. Environment variables defined in the managed settings file have high precedence and cannot be overridden by users.  Configuration Details  Common Configuration Variables Environment Variable Description Example Values CLAUDE_CODE_ENABLE_TELEMETRY Enables telemetry collection (required) 1 OTEL_METRICS_EXPORTER Metrics exporter type(s) (comma-separated) console , otlp , prometheus OTEL_LOGS_EXPORTER Logs/events exporter type(s) (comma-separated) console , otlp OTEL_EXPORTER_OTLP_PROTOCOL Protocol for OTLP exporter (all signals) grpc , http/json , http/protobuf OTEL_EXPORTER_OTLP_ENDPOINT OTLP collector endpoint (all signals) http://localhost:4317 OTEL_EXPORTER_OTLP_METRICS_PROTOCOL Protocol for metrics (overrides general) grpc , http/json , http/protobuf OTEL_EXPORTER_OTLP_METRICS_ENDPOINT OTLP metrics endpoint (overrides general) http://localhost:4318/v1/metrics OTEL_EXPORTER_OTLP_LOGS_PROTOCOL Protocol for logs (overrides general) grpc , http/json , http/protobuf OTEL_EXPORTER_OTLP_LOGS_ENDPOINT OTLP logs endpoint (overrides general) http://localhost:4318/v1/logs OTEL_EXPORTER_OTLP_HEADERS Authentication headers for OTLP Authorization=Bearer token OTEL_EXPORTER_OTLP_METRICS_CLIENT_KEY Client key for mTLS authentication Path to client key file OTEL_EXPORTER_OTLP_METRICS_CLIENT_CERTIFICATE Client certificate for mTLS authentication Path to client cert file OTEL_METRIC_EXPORT_INTERVAL Export interval in milliseconds (default: 60000) 5000 , 60000 OTEL_LOGS_EXPORT_INTERVAL Logs export interval in milliseconds (default: 5000) 1000 , 10000 OTEL_LOG_USER_PROMPTS Enable logging of user prompt content (default: disabled) 1 to enable  Metrics Cardinality Control The following environment variables control which attributes are included in metrics to manage cardinality: Environment Variable Description Default Value Example to Disable OTEL_METRICS_INCLUDE_SESSION_ID Include session.id attribute in metrics true false OTEL_METRICS_INCLUDE_VERSION Include app.version attribute in metrics false true OTEL_METRICS_INCLUDE_ACCOUNT_UUID Include user.account_uuid attribute in metrics true false These variables help control the cardinality of metrics, which affects storage requirements and query performance in your metrics backend. Lower cardinality generally means better performance and lower storage costs but less granular data for analysis.  Multi-Team Organization Support Organizations with multiple teams or departments can add custom attributes to distinguish between different groups using the OTEL_RESOURCE_ATTRIBUTES environment variable: export OTEL_RESOURCE_ATTRIBUTES = "department=engineering,team.id=platform,cost_center=eng-123" These custom attributes will be included in all metrics and events, allowing you to: Filter metrics by team or department Track costs per cost center Create team-specific dashboards Set up alerts for specific teams  Example Configurations export CLAUDE_CODE_ENABLE_TELEMETRY = 1 export OTEL_METRICS_EXPORTER = console export OTEL_METRIC_EXPORT_INTERVAL = 1000 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 export CLAUDE_CODE_ENABLE_TELEMETRY = 1 export OTEL_METRICS_EXPORTER = prometheus export CLAUDE_CODE_ENABLE_TELEMETRY = 1 export OTEL_METRICS_EXPORTER = console,otlp export OTEL_EXPORTER_OTLP_PROTOCOL = http/json 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.company.com:4318 export OTEL_EXPORTER_OTLP_LOGS_PROTOCOL = grpc export OTEL_EXPORTER_OTLP_LOGS_ENDPOINT = http://logs.company.com:4317 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 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 All metrics and events share these standard attributes: Attribute Description Controlled By session.id Unique session identifier OTEL_METRICS_INCLUDE_SESSION_ID (default: true) app.version Current Claude Code version OTEL_METRICS_INCLUDE_VERSION (default: false) organization.id Organization UUID (when authenticated) Always included when available user.account_uuid Account UUID (when authenticated) OTEL_METRICS_INCLUDE_ACCOUNT_UUID (default: true) terminal.type Terminal type (e.g., iTerm.app , vscode , cursor , tmux ) Always included when detected  Metrics Claude Code exports the following metrics: Metric Name Description Unit claude_code.session.count Count of CLI sessions started count claude_code.lines_of_code.count Count of lines of code modified count claude_code.pull_request.count Number of pull requests created count claude_code.commit.count Number of git commits created count claude_code.cost.usage Cost of the Claude Code session USD claude_code.token.usage Number of tokens used tokens claude_code.code_edit_tool.decision Count of code editing tool permission decisions count  Metric Details  Session Counter Incremented at the start of each session. Attributes : All standard attributes  Lines of Code Counter Incremented when code is added or removed. Attributes : All standard attributes type : ( "added" , "removed" )  Pull Request Counter Incremented when creating pull requests via Claude Code. Attributes : All standard attributes  Commit Counter Incremented when creating git commits via Claude Code. Attributes : All standard attributes  Cost Counter Incremented after each API request. Attributes : All standard attributes model : Model identifier (e.g., claude-3-5-sonnet-20241022)  Token Counter Incremented after each API request. Attributes : All standard attributes type : ( "input" , "output" , "cacheRead" , "cacheCreation" ) model : Model identifier (e.g., claude-3-5-sonnet-20241022)  Code Edit Tool Decision Counter Incremented when user accepts or rejects Edit, MultiEdit, Write, or NotebookEdit tool usage. Attributes : All standard attributes tool : Tool name ( "Edit" , "MultiEdit" , "Write" , "NotebookEdit" ) decision : User decision ( "accept" , "reject" ) language : Programming language of the edited file (e.g., "TypeScript" , "Python" , "JavaScript" , "Markdown" ). Returns "unknown" for unrecognized file extensions.  Events Claude Code exports the following events via OpenTelemetry logs/events (when OTEL_LOGS_EXPORTER is configured):  User Prompt Event Logged when a user submits a prompt. Event Name : claude_code.user_prompt Attributes : All standard attributes event.name : "user_prompt" event.timestamp : ISO 8601 timestamp prompt_length : Length of the prompt prompt : Prompt content (redacted by default, enable with OTEL_LOG_USER_PROMPTS=1 )  Tool Result Event Logged when a tool completes execution. Event Name : claude_code.tool_result Attributes : All standard attributes event.name : "tool_result" event.timestamp : ISO 8601 timestamp name : Name of the tool success : "true" or "false" duration_ms : Execution time in milliseconds error : Error message (if failed)  API Request Event Logged for each API request to Claude. Event Name : claude_code.api_request Attributes : All standard attributes event.name : "api_request" event.timestamp : ISO 8601 timestamp model : Model used (e.g., claude-3-5-sonnet-20241022) 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  API Error Event Logged when an API request to Claude fails. Event Name : claude_code.api_error Attributes : All standard attributes event.name : "api_error" event.timestamp : ISO 8601 timestamp model : Model used (e.g., claude-3-5-sonnet-20241022) error : Error message status_code : HTTP status code (if applicable) duration_ms : Request duration in milliseconds attempt : Attempt number (for retried requests)  Tool Decision Event Logged when a tool permission decision is made (accept/reject). Event Name : claude_code.tool_decision Attributes : All standard attributes event.name : "tool_decision" event.timestamp : ISO 8601 timestamp tool_name : Name of the tool (e.g., Read, Edit, MultiEdit, Write, NotebookEdit, etc.) decision : Either "accept" or "reject" source : Decision source - "config" , "user_permanent" , "user_temporary" , "user_abort" , or "user_reject"  Interpreting Metrics and Events Data The metrics exported by Claude Code provide valuable insights into usage patterns and productivity. Here are some common visualizations and analyses you can create:  Usage Monitoring Metric Analysis Opportunity claude_code.token.usage Break down by type (input/output), user, team, or model claude_code.session.count Track adoption and engagement over time claude_code.lines_of_code.count Measure productivity by tracking code additions/removals claude_code.commit.count & claude_code.pull_request.count Understand impact on development workflows  Cost Monitoring The claude_code.cost.usage metric helps with: Tracking usage trends across teams or individuals Identifying high-usage sessions for optimization Cost metrics are approximations. For official billing data, refer to your API provider (Anthropic Console, AWS Bedrock, or Google Cloud Vertex).  Alerting and Segmentation Common alerts to consider: Cost spikes Unusual token consumption High session volume from specific users All metrics can be segmented by user.account_uuid , organization.id , session.id , model , and app.version .  Event Analysis The event data provides detailed insights into Claude Code interactions: Tool Usage Patterns : Analyze tool result events to identify: Most frequently used tools Tool success rates Average tool execution times Error patterns by tool type Performance Monitoring : Track API request durations and tool execution times to identify performance bottlenecks.  Backend Considerations Your choice of metrics and logs backends will determine the types of analyses you can perform:  For Metrics: Time series databases (e.g., Prometheus) : Rate calculations, aggregated metrics Columnar stores (e.g., ClickHouse) : Complex queries, unique user analysis Full-featured observability platforms (e.g., Honeycomb, Datadog) : Advanced querying, visualization, alerting  For Events/Logs: Log aggregation systems (e.g., Elasticsearch, Loki) : Full-text search, log analysis Columnar stores (e.g., ClickHouse) : Structured event analysis Full-featured observability platforms (e.g., Honeycomb, Datadog) : Correlation between metrics and events For organizations requiring Daily/Weekly/Monthly Active User (DAU/WAU/MAU) metrics, consider backends that support efficient unique value queries.  Service Information All metrics are exported with: Service Name: claude-code Service Version: Current Claude Code version Meter Name: com.anthropic.claude_code  Security/Privacy Considerations Telemetry is opt-in and requires explicit configuration Sensitive information like API keys or file contents are never included in metrics or events User prompt content is redacted by default - only prompt length is recorded. To enable user prompt logging, set OTEL_LOG_USER_PROMPTS=1 Was this page helpful? Yes No Security Costs On this page Quick Start Administrator Configuration Configuration Details Common Configuration Variables Metrics Cardinality Control Multi-Team Organization Support Example Configurations Available Metrics and Events Standard Attributes Metrics Metric Details Session Counter Lines of Code Counter Pull Request Counter Commit Counter Cost Counter Token Counter Code Edit Tool Decision Counter Events User Prompt Event Tool Result Event API Request Event API Error Event Tool Decision Event Interpreting Metrics and Events Data Usage Monitoring Cost Monitoring Alerting and Segmentation Event Analysis Backend Considerations For Metrics: For Events/Logs: Service Information Security/Privacy Considerations

---
Document ID: en__docs__claude-code__monitoring-usage