ClickHouse Now Offers a Prometheus Drop-In Replacement

ClickHouse now supports PromQL, letting it act as a drop-in replacement for Prometheus to unify metrics, logs, and traces.

ClickHouse, the company behind the high-performance analytical database, has announced a new feature that directly targets the popular monitoring tool Prometheus. According to a post on the company's blog, ClickHouse now offers native support for PromQL, the query language used by Prometheus. This update effectively allows ClickHouse to function as a drop-in replacement for Prometheus's storage backend, enabling engineering and IT teams to store their system metrics directly within ClickHouse Cloud. The core promise is that users can continue using their existing Prometheus setups for data collection and querying without needing to rewrite anything in SQL, simplifying the migration process and lowering the barrier to entry for unifying their observability data.

The new capability is powered by a time-series engine built into ClickHouse. This isn't merely a compatibility layer or a data connector that translates queries; it's a fundamental integration that allows the database to understand and execute PromQL queries natively. When Prometheus scrapes metrics from various services, that data can be sent directly to a ClickHouse instance. From there, developers, site reliability engineers (SREs), and IT teams can use the exact same PromQL syntax they are familiar with to query, visualize in dashboards like Grafana, or set up alerts. This native implementation is key, as it avoids the performance overhead and potential inaccuracies of query translation, ensuring that the experience is seamless for anyone accustomed to the Prometheus ecosystem. It effectively separates Prometheus's data collection function from its storage, offering a more scalable and integrated alternative for the latter.

This move is a significant development in the broader trend of observability data consolidation. For the past decade, the standard practice for many organizations involved using a collection of specialized, "best-of-breed" tools: Prometheus for metrics, an ELK Stack (Elasticsearch, Logstash, Kibana) or Loki for logs, and Jaeger or Tempo for traces. While powerful, this approach creates data silos, forcing engineers to jump between different systems and query languages to troubleshoot a single issue. ClickHouse's strategy directly challenges this fragmented model by proposing a single, unified platform. By bringing metrics into the same database that might already hold application logs and business data, it enables teams to run powerful correlational analyses that were previously difficult or impossible. This follows a similar path as platforms like Datadog or Grafana's LGTM stack, which also aim to provide a single pane of glass for all telemetry data.

For companies already using ClickHouse for analytics or logging, this update presents a compelling opportunity to simplify their technology stack. Migrating metrics from a separate Prometheus setup can reduce infrastructure complexity, operational overhead, and potentially lower costs. For organizations deeply embedded in the cloud-native ecosystem and reliant on Prometheus, ClickHouse now emerges as a powerful, scalable backend alternative to solutions like Thanos or Cortex, without requiring them to abandon their investment in PromQL skills and tooling. The key factor to watch will be real-world performance and the completeness of the PromQL implementation compared to established standards. This move intensifies the competition among database and observability vendors, all vying to become the central repository for the growing volume of critical system data.

For developers and SREs, this eliminates the need to manage separate systems for metrics, logs, and traces. Unifying observability data in ClickHouse simplifies infrastructure, reduces operational overhead, and enables more powerful, cross-domain queries without context switching between different query languages like PromQL and SQL.

This move positions ClickHouse as a direct competitor to specialized observability platforms. By consolidating metrics, logs, and traces, companies can potentially lower licensing costs, reduce infrastructure complexity, and improve team efficiency. This simplifies the data stack, leading to faster troubleshooting and better operational insights.