Metrics monitoring built on the Elasticsearch Platform SREs trust

Elastic pairs best-in-class metrics efficiency with the industry's richest log analytics solution. 30x faster queries than competing TSDBs, built on a columnar datastore engineered for high-cardinality workloads that scale without breaking the bank. With native PromQL so you can keep the workflows you love.

Meet the columnar metrics engine that's best in its class

The Elasticsearch columnar datastore outpaces others in metrics ingest, storage, and query speed at any scale.

Scale without dropping data

The engineering depth that set the standard for log ingest, storage, and query performance is exactly what we applied to building a better TSDB for high-cardinality metrics. Same team, same rigor, new data type — built to retain every metric at full resolution without the price tag.

  • BEST-IN-CLASS EFFICIENCY

    Faster queries at a fraction of the cost

    Elasticsearch runs queries 25x faster than Prometheus and stores metrics 2.5x leaner — with no cardinality limits. Keep your current ingest architecture, retain more history, and pay less for it than a comparable Prometheus stack.

  • SCHEMA-AGNOSTIC

    One datastore, all formats

    Most backends normalize everything into a single schema. We don't. Whether you send us Prometheus, OpenTelemetry, Beats, or OCSF, Elasticsearch stores each in its native format and queries it as-is. No translation layer, no information loss, no conversion tax.

  • ONE-DAY MIGRATION

    PromQL from day one

    Your existing PromQL queries, dashboards, and alert rules carry over without having to learn a new language. Remote write and OTLP ingest are both supported. Migration is a configuration change, not a month-long project.

  • LOGS + METRICS + TRACES

    Unified investigations — no context switching required

    In a typical observability stack, finding root cause often means navigating multiple query languages and backends. In Elasticsearch, metrics, logs, and traces are all in one place. When an alert fires, the relevant context is already there.

Elasticsearch doesn't scan rows. It reads columns.

Elasticsearch's segment-based storage is columnar by design, ensuring sub-second response on millions of time series with vector loading and processing.

  • Query any data at high cardinality

    ES|QL is built to exploit this: a vectorized query engine that processes data in batches and doesn't degrade at high cardinality. Pipe queries across metrics, logs, and traces — with native PromQL support included.

  • Get more from every byte

    Elasticsearch includes a full set of time-series functions for rate, delta, percentile, bucketing, and aggregations. Storage optimizations like doc value skippers and synthetic ID trimming keep costs down as data grows.
  • Access from anywhere you already work

    Most backends give you one way in. Elasticsearch gives you three: Kibana for dashboards and prebuilt workflows, Elastic AI Agent for chat-led investigations, and purpose-built MCP apps and skills for the AI tools your team already works in.

ELASTICSEARCH 9.4 BENCHMARKS

Engineering that shows up in the numbers

Head-to-head across the three metrics that define a production-grade TSDB: query speed, storage density, and ingest throughput

Dimension Elasticsearch 9.4 Prometheus Mimir ClickHouse
Query speedHigh-cardinality time series Fastest
Baseline
Up to 30x slower Up to 30x slower Up to 8x slower
Storage densityBytes/sample Best
3.74 B
~9.42 B ~3.95 B ~6.8 B
Ingest throughputSamples/second Fastest
428K/s
402K/s 404K/s ~300K/s
Native PromQLNo adapter required Native ✓ Native ✓ Native Requires adapter
OTel-nativeNo schema conversion OTel-first Via exporters Via exporters Manual mapping

THE INNOVATION THAT MADE IT POSSIBLE

Building the Elasticsearch columnar metrics engine

From storage architecture to query execution, each part of our platform was built with purpose. Here's the engineering that made it real.

Migration tool — tech preview

Migrate from Datadog or Grafana overnight

Automatically convert dashboards and alerting rules from Datadog and Grafana into Elastic, dramatically reducing the cost and complexity of switching platforms.

Ready to switch and save 50% on your Datadog metrics bill?

Start shipping Prometheus metrics to Elastic

The Prometheus Remote Write endpoint requires no extra configuration. Once metrics are flowing, you can query them with ES|QL using the built-in PROMQL function for PromQL compatibility, or write native ES|QL queries to join metrics with logs and traces in the same store.

Turn metrics into action

Monitor your infrastructure at scale. Explore metrics in Discover, build dashboards as code, and let AI-led investigations highlight anomalies, uncover trends, and automate remediation, so you can plan capacity and resolve issues faster.

Frequently asked questions

Can Elasticsearch replace Prometheus for metrics monitoring?

Yes. Elasticsearch includes a native Prometheus Remote Write endpoint, PromQL support via the built-in PROMQL function in ES|QL, and a columnar metrics engine designed for high-cardinality time series. Teams can migrate from Prometheus in a day by automatically converting their existing Grafana dashboards and alert rules.

How does Elasticsearch compare to Prometheus for query speed?

In Elasticsearch 9.4 benchmarks, Elasticsearch queries high-cardinality time series up to 30x faster than Prometheus. Storage efficiency is also higher: Elasticsearch stores metrics at 3.74 bytes per sample, compared to approximately 9.42 bytes for Prometheus.

Does Elasticsearch support OpenTelemetry (OTel) metrics natively?

Yes. Elasticsearch is OTel-first and ingests metrics in their native OpenTelemetry format without schema conversion. Prometheus, Beats, and OCSF formats are also supported natively, each stored as-is without a translation layer.

How long does it take to migrate from Datadog or Grafana to Elasticsearch?

Elastic provides a migration tool (currently in tech preview) that automatically converts Datadog and Grafana dashboards and alerting rules into Elastic/Kibana format. For Prometheus migration, connecting Prometheus Remote Write to Elasticsearch requires only a configuration change.

What is a TSDB and why does it matter for metrics monitoring?

A TSDB (time series database) is a database optimized for storing and querying data indexed by time, like infrastructure metrics. Elasticsearch's time series data streams (TSDS) use a columnar storage engine that processes data in batches and applies synthetic ID trimming and doc value skippers to reduce storage size, making it faster and cheaper than traditional row-based alternatives.

What makes columnar storage faster for metrics queries?

Columnar storage makes metrics queries faster because it reads only the data columns relevant to a query rather than scanning entire rows. In a time series workload, this means the database can pull just the values it needs — say, CPU usage over a 24-hour window — without touching unrelated fields. Elasticsearch takes this further with a vectorized query engine that processes data in batches, enabling sub-second response times even across millions of time series at high cardinality.