Telemetry

If you ship OpenTelemetry data into ClickHouse (via the OTel ClickHouse exporter or your own pipeline), the Telemetry page gives you a purpose-built log explorer on top of it — no Grafana or Kibana needed for the everyday "what just happened" check.

Setup

There is almost none. CH-UI auto-detects OTel tables (otel_logs, otel_traces, otel_metrics) in your connected ClickHouse. If your tables live in a different database or use different names, point Telemetry at them in the page's configuration.

If no tables are found, a setup wizard walks you through the options.

Logs explorer

• Severity filtering — narrow to errors/warnings instantly
• Service breakdown — see which services are producing logs, and filter by service
• Volume histogram — log volume over time, so spikes stand out before you scroll
• Time-range controls with live querying — everything is computed by ClickHouse on demand; CH-UI stores nothing

Brain integration

The Brain AI assistant has telemetry tools built in (query_logs, query_traces, list_services, query_metrics) and a curated otel-triage skill pack — you can ask things like "show me error logs for the checkout service in the last hour" in plain language and get the underlying query back.

Roadmap

Traces and metrics exploration views are in progress — the data layer (and the Brain tools above) already speak traces and metrics; dedicated UI tabs are next.

Requirements

• OTel data in ClickHouse — any schema the ClickHouse exporter produces works out of the box
• Telemetry is part of the open-source core — no license required