Monitor your Claude Code usage with Cloudflare Workers and Workers Analytics Engine.

• Public, Secure endpoint for OpenTelemetry/OTLP
• Powerful analytics via ClickHouse SQL
• Truly Serverless, zero-maintenance

One-click deployment with

Monitoring via OpenTelemetry is the Claude Code built-in feature.

Once you deploy the worker to the https://cc-monitor.your-org.workers.dev, you can enable monitoring with env settings like:

{
  "env": {
    "CLAUDE_CODE_ENABLE_TELEMETRY": "1",

    // Currently support metrics only
    "OTEL_METRICS_EXPORTER": "otlp",
    "OTEL_EXPORTER_OTLP_PROTOCOL": "http/json",
    "OTEL_EXPORTER_OTLP_ENDPOINT": "https://cc-monitor.your-org.workers.dev",
    "OTEL_METRIC_EXPORT_INTERVAL": 10000,

    // See security section below
    "OTEL_EXPORTER_OTLP_HEADERS": "Authorization=Bearer token"
  }
}

You can leverage your company's MDM solution to deploy this as org-managed settings.

See more details from the Claude Code official guide.

You can query the collected data in the Cloudflare Console (Analytics Engine Studio), Cloudflare API or Grafana Dashboard.

Blobs (Fixed Schema):

• blob1: metric_type (session_count, cost_usage, etc.)
• blob2: service.name (e.g. claude-code)
• blob3: service.version (e.g. 1.0.48)
• blob4: organization.id (UUID)
• blob5: user.id (hashed user ID)
• blob6: user.account_uuid (UUID)
• blob7: user.email (email address)
• blob8: session.id (UUID)
• blob9: terminal.type (e.g. iTerm)
• blob10+: Metric-specific attributes

Doubles:

• double1: timestamp_ms - Timestamp in milliseconds
• double2: metric_value - The actual metric value

The endpoint processes the following Claude Code metrics:

SELECT 
  blob1 as metric_type,
  blob7 as user_email,
  SUM(double2) as total_value
FROM claude_code_metrics_{{SCHEMA_VERSION}}
WHERE metric_type = 'cost_usage'
GROUP BY metric_type, user_email
ORDER BY total_value DESC

Claude Code → OTLP/HTTP → Cloudflare Worker → Analytics Engine

The worker acts as a bridge between Claude Code's OTLP metrics and Cloudflare's Analytics Engine:

1. Receives OTLP metrics via HTTP/JSON POST requests
2. Authenticates requests using Bearer token validation
3. Transforms OTLP data to Analytics Engine format
4. Stores metrics in Analytics Engine for querying

The endpoint uses Bearer token authentication:

• Development: Set AUTH_SECRET in .dev.vars
• Production: Use wrangler secret put AUTH_SECRET

Use strong, randomly generated secrets and rotate secrets regularly.

MIT