---
title: "PromQL"
description: "2 posts about PromQL, summarised, each linking to the original."
---

# PromQL
> 2 posts about PromQL, summarised, each linking to the original.

## Articles

### [September 2026 newsletter](https://yomu.fyi/post/september-2026-newsletter.md)
- Company: [Clickhouse](https://yomu.fyi/company/clickhouse.md)
- Published: Sep 17, 2026
- Type: Announcement

The September 2026 ClickHouse newsletter gathers product updates, community contributions, technical articles, and upcoming events. Its main release coverage describes ClickHouse 26.8, including custom HTTP handlers, dynamic query filtering, pipelined SQL through the |> operator, current-user query logging, a URL database engine, and Japanese and Chinese text-index tokenizers. Other featured developments include On-Demand Compute in private preview with a cost-based optimizer and distributed query execution, PromQL and a TimeSeries engine in private preview, AI Functions, and Postgres integrations such as WalShadow and Managed Postgres on Google Cloud. The issue also reports CostBench’s first end-to-end performance-per-dollar results, explains replication-queue diagnosis, notes 57 breaking changes since 26.3, and lists training, webinars, roadshows, and other events.


### [Introducing ClickHouse's new TimeSeries Engine: Your drop-In Prometheus replacement](https://yomu.fyi/post/introducing-clickhouse-s-new-timeseries-engine-your-drop-in-prometheus.md)
- Company: [Clickhouse](https://yomu.fyi/company/clickhouse.md)
- Published: Sep 15, 2026
- Type: Announcement

ClickHouse announces the private preview of PromQL and its TimeSeries table engine in ClickHouse Cloud, allowing Prometheus metrics to be sent through remote write and queried in ClickStack, Grafana, or ClickHouse. Prometheus metrics are shaped by pull-based collection: applications expose current state, collectors add scrape-time timestamps, and types such as counters, gauges, histograms, and summaries determine interpretation. PromQL preserves the resulting semantics, including counter reset handling, range-window extrapolation, and histogram bucket processing, rather than requiring teams to reproduce those rules in SQL or a translation layer. The announcement describes limited preview access, says supported functions and operators are documented separately, and identifies future work around downsampling, native histograms, rules, additional protocols, and direct OpenTelemetry export.