RousselTMLEARNING

Article · ClickStack: from discovery to expertise

Exploring with the ClickStack UI

1. Sources #

What the UI queries.

The principle #

Available in: ✓ Open source ✓ Managed ClickStack

A source describes a ClickHouse table and how to read it: time column, message body, level, service name, trace IDs. ClickStack creates default sources with the first account; you can add more for any ClickHouse table, including your own data.

SourceTableUse
Logsotel_logssearch, live tail, charts
Tracesotel_tracesspan search, waterfall, latency
Metricsotel_metrics_gauge, _sum, _histogram…charts and dashboards
Sessionshyperdx_sessionsbrowser session replay
Best practice : Link sources together (logs ↔ traces ↔ sessions) in their settings: that is what enables correlation links in the UI.

2. Searching #

Properties, full text or SQL.

Search syntax #

SearchFinds
timeoutevents whose body contains “timeout”
"connection refused"the exact phrase
level:errerror level (property)
service:checkout level:errboth conditions (implicit AND)
service:checkout OR service:paymentseither one
-level:info / NOT level:infoexclude
http.status_code:500an attribute (Map column key)

The SQL mode accepts a WHERE condition directly: SeverityText = 'error' AND LogAttributes['http.route'] LIKE '/api/%'. Handy for ClickHouse functions (regular expressions, numeric comparisons).

Exploring results #

  • Live tail: new events stream in during a release or a test.
  • Histogram of event counts over time: click and drag to zoom into a spike.
  • Columns: add an attribute as a column, filter on a value in one click from an event's details.
  • Saved searches: reusable, shareable, and the basis of alerts.

3. Traces, logs and sessions #

Correlating signals.

The journey #

Correlation in ClickStack
  • Trace: the waterfall shows each span, its duration and attributes; logs emitted during each span are shown alongside.
  • From log to trace: a log carrying a TraceId opens the full request trace.
  • From trace to session: if the browser SDK is in place, the user's session, journey and replay.

A typical investigation #

  1. An alert reports errors: search service:checkout level:err over the last hour.
  2. The histogram shows when it started; a log's details give the faulty http.route attribute.
  3. Open the trace: the longest span is a database call timing out.
  4. The session shows the user's action and the error message displayed.
  5. Measure the scope in SQL (number of users affected) before communicating.

4. Going further with SQL #

When the UI is not enough.

Useful queries #

-- Distinct users affected by the error over the last hour
SELECT uniq(LogAttributes['user.id']) AS users
FROM otel_logs
WHERE ServiceName = 'checkout' AND SeverityText ILIKE 'err%' AND Timestamp > now() - INTERVAL 1 HOUR;

-- Slowest routes (p95) from traces
SELECT SpanAttributes['http.route'] AS route, quantile(0.95)(Duration) / 1e6 AS p95_ms, count() AS calls
FROM otel_traces
WHERE ServiceName = 'checkout' AND SpanKind = 'Server' AND Timestamp > now() - INTERVAL 1 HOUR
GROUP BY route ORDER BY p95_ms DESC LIMIT 10;
Good to know : In Managed ClickStack, AI-assisted notebooks help write these analyses; always check the generated query before trusting the result.

Commands to know #

Commands to know
  • service:checkout level:err : property search
  • "connection refused" : exact phrase
  • -level:info : exclusion
  • LogAttributes['http.route'] : read an attribute in SQL
  • quantile(0.95)(Duration) / 1e6 : p95 latency in milliseconds

Sources #

Checked in November 2026: ClickStack evolves fast (Managed ClickStack is in beta), check the ClickHouse documentation before relying on a detail.

📄 Exploring with the ClickStack UI: sources, search, traces, sessions and SQL →

My progress

  • ⏱ Estimated time : ≈ 5 min

Sign in to track your progress and take notes. Sign in

💬 Questions about this lesson

No questions yet: be the first to ask for help or share your configuration.

Ask a question about this lesson →

Recommended Articles

Sending telemetry to ClickStack: OpenTelemetry SDKs, collectors, logs, Kubernetes and browser sessions

Feeding ClickStack: ingestion key, OpenTelemetry SDK variables, forwarding through an existing co...

Alerts and dashboards in ClickStack

Building charts and dashboards in ClickStack, creating alerts on a search or a chart, sending the...

Observability on ClickHouse: why a columnar database changes the game

Why more and more observability platforms store logs, traces and metrics in ClickHouse: columnar ...

Telemetry in ClickHouse: schema, SQL, materialized views and retention

Telemetry in ClickHouse: otel_logs, otel_traces, otel_metrics_* and hyperdx_sessions tables, sort...

SigNoz, ClickStack and ClickHouse best practices for observability

Best practices for observability on ClickHouse with SigNoz or ClickStack: OpenTelemetry instrumen...

ClickStack: architecture, components and offerings (ClickHouse, HyperDX, OpenTelemetry)

ClickStack, ClickHouse's official observability stack: role of ClickHouse, the UI (HyperDX), the ...

Exploring data in Discover: KQL, Lucene and ES|QL

Search and analyze logs in Kibana Discover: filters, KQL, Lucene syntax, and the ES|QL language t...

Operating ClickHouse for ClickStack: sizing, replication, monitoring, security and backup

Running ClickHouse in production for observability: estimating volume and disk, replicating with ...

Operating an observability platform on ClickHouse and choosing a tool

Operate ClickHouse for telemetry (replication, disks, merges, object storage, monitoring) and com...

Support us

♥ SUPPORT US

Support RousselTM Learning

Courses, articles, labs and certificates stay free with no intrusive ads. A voluntary contribution, of any amount you choose, pays for hosting, lab environments and new content.

Contribute with PayPal Any amount · card or PayPal accountLearn more
QR code PayPal
Or scan this QR code with your phone

Thank you, every contribution counts!