administration

# Claude Code Administration

## Monitoring Overview

Claude Code supports **OpenTelemetry (OTel) for metrics and events**. The system exports time series data via standard metrics protocol and events through logs/events protocol.

### Quick Setup

Enable telemetry:
```bash
export CLAUDE_CODE_ENABLE_TELEMETRY=1
```

Configure exporters (optional, pick what you need):
```bash
# Metrics
export OTEL_METRICS_EXPORTER=otlp  # Options: otlp, prometheus, console

# Logs
export OTEL_LOGS_EXPORTER=otlp     # Options: otlp, console
```

### Export Intervals

Default intervals:
- **Metrics**: 60 seconds
- **Logs**: 5 seconds

Customize intervals:
```bash
export OTEL_METRIC_EXPORT_INTERVAL=30000  # milliseconds
export OTEL_LOGS_EXPORT_INTERVAL=10000    # milliseconds
```

## Available Metrics

Claude Code tracks eight core metrics:

### 1. Session Counter
CLI sessions started

**Use for:** Tracking adoption and active users

### 2. Lines of Code
Code additions/removals tracked by type

**Use for:** Measuring productivity and code generation volume

### 3. Pull Requests
Creation count

**Use for:** Tracking automated PR generation

### 4. Commits
Git commits via Claude Code

**Use for:** Measuring development activity

### 5. Cost Usage
Session costs in USD (model-segmented)

**Use for:** Budget tracking and cost allocation

**Important:** Cost metrics are approximations. For official billing data, refer to your API provider (Claude Console, AWS Bedrock, or Google Cloud Vertex).

### 6. Token Usage
Tokens consumed (input/output/cache types)

**Use for:** Understanding API usage patterns and optimizing costs

### 7. Code Edit Tool Decisions
Accept/reject counts per tool

**Use for:** Understanding user trust and automation acceptance

### 8. Active Time
Actual usage duration in seconds

**Use for:** Measuring engagement and productivity time

## Metric Segmentation

Segment metrics by:
- `user.account_uuid` - Individual user tracking
- `organization.id` - Team/organization groupi