Skip to main content
This page documents all OpenTelemetry log events currently instrumented in Cline. These events are emitted when OpenTelemetry integration is enabled and provide detailed insights into user behavior, task execution, and system operations.
Events are only emitted when OpenTelemetry is enabled. See OpenTelemetry for configuration instructions.

Event Categories

Cline emits events across several categories, each prefixed with a namespace:

user.*

Authentication, telemetry controls, extension lifecycle

task.*

Task execution, conversation turns, tool usage, tokens

workspace.*

Workspace initialization, VCS detection, path resolution

ui.*

User interface interactions and model selection

hooks.*

Hook discovery, execution, and context modification

worktree.*

Git worktree operations and merge handling

host.*

Host environment detection

test.*

Diagnostic and connection testing

User Events

Events related to user authentication, telemetry preferences, and extension lifecycle.

Example: user.auth_succeeded

Workspace Events

Events related to workspace initialization, version control detection, and multi-root operations.

Example: workspace.initialized

Task Events

Core events tracking task lifecycle, conversation turns, tool usage, and execution details.

Task Lifecycle

Conversation & Tokens

Tool Usage

Features & Options

Advanced Features

Auto-Compact & Context

Settings & Features

API & Performance

AI Output Feedback

Example: task.tool_used

UI Events

Events tracking user interface interactions.

Example: ui.model_selected

Hooks Events

Events related to hook discovery, execution lifecycle, and context modifications.

Hook Execution Lifecycle

The hooks.execution event tracks the complete lifecycle with a status attribute:
  • started: Hook execution began
  • completed: Hook finished successfully
  • failed: Hook encountered an error
  • cancelled: Hook was cancelled by user or system

Example: hooks.execution

Worktree Events

Events related to Git worktree operations.

Example: worktree.created

Host Events

Events related to host environment detection.

Example: host.detected

Test Events

Diagnostic and connection testing events.

Example: cline.test.connection

Event Attribute Guidelines

Common Attributes

Most events include these standard attributes:

Privacy & Hashing

Sensitive information is hashed or anonymized:
  • File paths: Hashed to preserve privacy
  • Command content: Hashed, not logged verbatim
  • User identifiers: Anonymized tokens
  • Branch names: Hashed in worktree events
File paths, command arguments, and code content are never included in raw form. Only hashes or anonymized identifiers are used.

Task Event Deep Dive

Task events are the most detailed category. Here’s a typical task execution flow:

Task Token Tracking

Token events provide detailed cost and usage information:

Using Events for Analytics

SQL syntax is illustrative only. Attribute access varies by observability platform — for example, JSON_EXTRACT(attributes, '$.model') in BigQuery, attributes['model'] in ClickHouse, or @attributes.model in Datadog. Adapt all queries below to your platform’s query language before use.

Query Patterns

Most used tools:
Average task duration by model:
Token usage by provider:
Tool approval rates:

Integration Examples

Query syntax below is illustrative. Attribute access varies by platform — for example, JSON_EXTRACT(attributes, '$.model') in BigQuery, attributes['model'] in ClickHouse, or dot notation in Datadog. Adapt to your platform’s query language.

Datadog Dashboard

Create custom Datadog dashboards using these events:

Grafana Queries

Example Loki query for tool usage:

New Relic NRQL

Query task completion rates:

Event Schema Reference

All events follow this structure:

Best Practices

Filter Noise

Focus on events relevant to your use case. Not all events need dashboards.

Set Alerts

Alert on error events and usage anomalies for proactive monitoring.

Aggregate Metrics

Roll up events into metrics for long-term trend analysis.

Respect Privacy

Remember events are already anonymized. Don’t attempt to de-anonymize.

Troubleshooting

Events Not Appearing

If events aren’t showing up in your observability platform:
  1. Verify OTel is enabled in remote configuration or environment variables
  2. Check endpoint configuration - ensure URL and protocol are correct
  3. Validate credentials - test with the “Test OTEL Connection” button
  4. Check exporter settings - ensure logs exporter includes otlp
  5. Review platform-specific requirements - some platforms need specific headers

Event Volume Concerns

If you’re seeing excessive event volume:
  1. Sample events - Configure sampling in your OTel collector
  2. Filter events - Use your platform’s filtering to drop noisy events
  3. Aggregate on collection - Pre-aggregate metrics before export
  4. Adjust export intervals - Increase openTelemetryMetricExportInterval and batch settings

See Also

OpenTelemetry Setup

Configure OTel integration

Prompt Storage

Backup conversation history

Telemetry

Basic telemetry overview