Documentation

Click-Dog reads query spans from ClickHouse system.opentelemetry_span_log and exports them to OTLP-compatible backends and Splunk HEC. Start with Getting Started, then branch into your backend and your operations from the sections below.

Get started

• Getting Started

  From a fresh host to a running export.

• Install

  Run Click-Dog as a systemd service, a container, or a single binary.

• Configuration

  The full YAML reference — every key, default, and env-var override.

Integrations

• Datadog

  The packaged path: OTLP export, provisioned dashboards, and self-monitoring.

• Honeycomb

  Export traces to Honeycomb through an OpenTelemetry Collector.

• Generic OTLP

  Send to any OTLP/gRPC backend — Tempo, Jaeger, Elastic APM, and more.

• Splunk HEC

  Fan out span-shaped query events to Splunk HTTP Event Collector.

Query analysis

• Query Analysis

  Explain query behavior, not just export spans.

• Span Attributes

  Every attribute carried on the spans Click-Dog exports.

Operate

• Observability

  Watch Click-Dog itself: structured logs, Prometheus metrics, webhooks.

• Resilience

  Circuit breaker and adaptive backoff that protect ClickHouse and Click-Dog.

• Troubleshooting

  Diagnose common issues, starting with debug logging.

• Operating Contract

  What the public beta guarantees — and what it doesn't.

• Kubernetes — ClickHouse Setup

  Deploy the collector side against a ClickHouse operator.

Reference

• Operation Modes

  Scheduled, backfill, validation, dry-run, analysis, and manifest generation.

• Filtering

  The layers that decide which spans get exported.

• Architecture

  How the single Go binary sits beside your database.

• Changelog

  Notable changes across releases.

• Support

  Community and commercial support paths.