claudeotel-settings (claudeotel: )
Claude OTel settings (claudeotel: )
Claude Code usage tracking is handled by hivel-agent and the Claude OTel Collector, bundled together into a single Docker image. Unlike the other integrations on this page, it needs its own setup, since it needs an open port for your developers' machines to reach it.
Installation: the combined image is included in the same package as hivel-agent. No separate download or extraction step is needed.
Running it:
Ports and network: The Collector accepts inbound OTLP traffic from your developers' machines on TCP 4317 (gRPC) and/or TCP 4318 (HTTP), whichever your Claude Code clients use. Open whichever port(s) apply on the hivel-agent host. No other port needs to be exposed externally.
What data flows through it: The Collector receives Claude Code usage events from your developers' machines and hands them to hivel-agent. hivel-agent then pulls from the Collector the same way it pulls from Jira, GitHub, and your other sources, and uploads that data to Hivel through its normal sync process. What's included in claude_events.jsonl depends on which OTEL_LOG_* flags you've enabled in Claude Code's own settings. There is currently no redact_names_and_urls / strip_text_content equivalent for this provider.
Credentials: Sync --provider claudeotel requires your HIVEL_API_TOKEN, same as any other provider. It does not need a separate source credential today, api_key below is a non-functional placeholder reserved for future use.
For how to configure Claude Code itself to point at your on-prem setup, see Claude On-Prem.
Key
Required
Default
Description
instance_slug
Yes (multi-instance)
-
Unique ID for this claudeotel instance
base_url
No
https://otel-collector.hivel.ai/api
OTel collector base URL - override with your on-prem VM's address if self-hosting the collector
api_key
No
dummy-value
OTel collector auth key - currently non-functional / futureproofing
org_id
No
your Hivel org id
Hivel org id scoping OTel collector API requests
Last updated