Claude Code Agent Telemetry Integration

minware can receive telemetry data from Claude Code via the OpenTelemetry Protocol (OTLP/HTTP). This lets you capture detailed usage data — logs, metrics, and traces — directly in minware as a custom data source, without any schema mapping or transformation.

Claude Code telemetry data is fully queryable via minQL and can be used in any custom report.

Prerequisites

• You must be an account owner to create integrations.
• You need a minware API key to authenticate telemetry requests. You can create one at Settings > API Keys.

Create an Open Telemetry Integration

1. In minware, go to Settings > Data Sources > Integrations.
2. Under Custom Upload, click OpenTelemetry.
3. Fill in the Integration Display Name, an optional Description, and a lowerCamelCase minQL Reference Name (used to query the data in reports).
4. Click Create.

After creation, the Setup dialog will display your endpoint URL. You can reopen this dialog at any time by clicking Setup next to the integration.

Configure Claude Code

Personal setup

To configure Claude Code for your own account, add the following to your user-level ~/.claude/settings.json file. You can also place this in a project-level .claude/settings.json to apply it only within a specific project.

{
  "env": {
    "CLAUDE_CODE_ENABLE_TELEMETRY": "1",
    "OTEL_EXPORTER_OTLP_ENDPOINT": "<YOUR_ENDPOINT_URL>",
    "OTEL_EXPORTER_OTLP_HEADERS": "Authorization=Bearer <YOUR_API_KEY>",
    "OTEL_EXPORTER_OTLP_PROTOCOL": "http/json",
    "OTEL_LOGS_EXPORTER": "otlp",
    "OTEL_LOG_TOOL_CONTENT": "1",
    "OTEL_LOG_TOOL_DETAILS": "1",
    "OTEL_LOG_USER_PROMPTS": "1",
    "OTEL_METRICS_EXPORTER": "otlp",
    "OTEL_TRACES_EXPORTER": "otlp"
  }
}

The correct endpoint URL is shown in the Setup dialog after creating the integration — you can copy it directly from there, or download a pre-filled settings.json using the Download claude-code settings.json button.

Tip: OTEL_LOG_TOOL_CONTENT, OTEL_LOG_TOOL_DETAILS, and OTEL_LOG_USER_PROMPTS enable detailed tool-call and prompt logging. Remove any of these if you prefer not to capture that data. That data will appear as <REDACTED> in your reports.

Organization-wide setup (managed settings)

Administrators can push this configuration to all users without requiring individual setup by using Claude Code's managed settings file. Settings in the managed file have high precedence and cannot be overridden by users.

Add the same env block shown above to your organization's managed settings.json:

{
  "env": {
    "CLAUDE_CODE_ENABLE_TELEMETRY": "1",
    "OTEL_EXPORTER_OTLP_ENDPOINT": "<YOUR_ENDPOINT_URL>",
    "OTEL_EXPORTER_OTLP_HEADERS": "Authorization=Bearer <YOUR_API_KEY>",
    "OTEL_EXPORTER_OTLP_PROTOCOL": "http/json",
    "OTEL_LOGS_EXPORTER": "otlp",
    "OTEL_LOG_TOOL_CONTENT": "1",
    "OTEL_LOG_TOOL_DETAILS": "1",
    "OTEL_LOG_USER_PROMPTS": "1",
    "OTEL_METRICS_EXPORTER": "otlp",
    "OTEL_TRACES_EXPORTER": "otlp"
  }
}

Distribute this file via MDM (Mobile Device Management) or another device management solution. Refer to the Claude Code settings documentation for the exact paths and precedence rules on each platform.

Authentication

minware API keys are used to authenticate telemetry requests. Pass your API key as a Bearer token in the Authorization header (or via OTEL_EXPORTER_OTLP_HEADERS):

Authorization: Bearer <YOUR_API_KEY>

API keys carry the permissions of the user who created them. Only users with owner permissions can send data to an integration. If the API key is expired or the user is removed from the org, requests will be rejected.

Treat your API key like a password. Keep it secret and rotate it regularly.

Note: Only OTLP/JSON is supported. OTLP/Protobuf (binary format) is NOT supported.