Loading post…
ClickhouseThe ClickStack TeamAnnouncement
What's new in ClickStack - April 2026
Summary
ClickStack's April release introduces several core enhancements across querying, alerting, and dashboard visualization capabilities. The platform added SQL-powered alerting, allowing teams to express complex statistical rules like rolling baselines and anomaly detection using native ClickHouse SQL and window functions without external pipelines. To improve search and filtering performance across common observability workloads, the default otel_logs schema was redesigned with ClickHouse text indexes and adjusted ordering keys. Furthermore, heatmaps transitioned into a first-class chart type inside the shared visualization system for latency distribution tracking. The update also delivers persistent alert execution error reporting, expanded threshold comparison operators, and per-series number formatting across dashboards.
Context
UI-constrained query builders and static thresholding made statistical alerting awkward, often forcing teams to route rolling baselines or anomaly checks into external systems despite storing observability data in ClickHouse. Additionally, profiling recurring query patterns revealed that settings tuning alone could not resolve performance bottlenecks in the default log schema.
Approach / What changed
ClickStack implemented SQL-native alerts that execute ClickHouse SQL queries directly with dashboard macro support. They redesigned the default otel_logs schema around text indexes and updated primary ordering keys, moved heatmaps to the shared dashboard chart editor, persisted alert execution errors in the UI, and added per-series number formatting.
Takeaways
SQL-powered alerting in ClickStack enables complex logic such as rolling statistical baselines and anomaly detection using ClickHouse window functions and visualization macros.
The redesigned default otel_logs schema incorporates text indexes on trace IDs and attribute maps, alongside updated ordering keys, to improve filtering and search performance.
Alerting workflows now surface compilation and webhook execution errors in the UI, allowing operators to distinguish between inactive alerts and failed runs.
Source and freshness
- Source
- clickhouse.com
- Published
- Added to Yomu
- Last updated
Summaries are generated from the original by a language model. Check the original before relying on it.
Keep reading
Related reading
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
The best engineering reads, once a week
One useful email. Unsubscribe anytime.