Skip to main content

Elastic Adds Native Prometheus and PromQL Support to Elastic Observability

Unify Prometheus metrics with logs and traces, without rewriting queries or rebuilding pipelines

Elastic announced native Prometheus support, including direct ingestion via Remote Write and full PromQL support in Kibana.

These additions enable Site Reliability Engineers (SREs) to analyze Prometheus metrics alongside logs and traces in a single platform, without rewriting queries or rebuilding pipelines.

As organizations scale Kubernetes, Prometheus telemetry cardinality and volumes surge, forcing SREs to juggle multiple tools, duplicate data pipelines, and rewrite queries across systems. This fragmentation slows incident response and drives up operational costs.

With native Prometheus support, Elastic eliminates these fragmentation trade-offs by allowing teams to ingest, store, and analyze native Prometheus data alongside other telemetry data, while preserving existing Prometheus workflows. Instead of stitching together tools, SREs can detect, investigate, and resolve incidents end-to-end across AI and cloud-native environments faster and with less operational overhead.

“Modern incident response is slowed down by tool sprawl and disconnected data, and SREs shouldn’t have to pivot between tools or rewrite queries just to understand what’s happening in production,” said Bahaaldine Azarmi, general manager, Observability at Elastic. “With native Prometheus ingestion and PromQL in Kibana, teams get a single platform that dramatically reduces time to root cause.”

Native Prometheus Ingestion—No Translation Required (tech preview)

Elastic now ingests Prometheus metrics directly via Remote Write, eliminating the need for adapters, schema, or format translations.

SREs can stream Prometheus metrics straight into Elasticsearch while maintaining their original structure and semantics. The result is a single source of truth for observability, without forcing teams to abandon Prometheus. This approach:

  • Removes duplicate storage and pipeline complexity
  • Preserves full metric fidelity and high-cardinality data
  • Enables unified analysis across metrics, logs, and traces

Run PromQL Directly in Kibana (tech preview)

With native PromQL support in Kibana, users can run existing PromQL queries in dashboards and alerts without modification, lowering the barrier to adoption for teams already using Prometheus.

This eliminates query rewrites, one of the biggest adoption barriers in observability platforms. SREs can keep the PromQL they’ve already built, including dashboards, alerts, and workflows, alongside logs and traces in the same environment, while gaining a path from alert to root cause without manual pivoting, enabling deeper, cross-signal analysis during incidents.

Availability

Native Prometheus ingestion and PromQL support in Kibana are available in technical preview.
 

The Latest

I've spent a lot of time in the channel, and one thing I keep coming back to is this: a partner program is only as good as what it looks like in the field. Many programs look great on paper, but when a partner is in front of a customer navigating a complex hybrid environment or trying to make the case for AI-powered observability, the gap between what a vendor promises and what it actually delivers becomes very clear, very fast ...

Enterprises today operate in a real-time environment where uninterrupted access to trusted data has become a baseline expectation for users, applications and automated systems. Traditional DataOps models, built on manual effort and human triage, cannot keep pace with this always active demand. AI agents are emerging as the operational backbone, ensuring consistent data availability, reinforcing trustworthiness and enabling a level of scale that manual processes cannot achieve ...

For decades, trust in the digital workplace rested on familiar signals. We trusted faces on video calls, voices on the phone, and emails that appeared to come from people we knew. These cues felt human and intuitive. They anchored how decisions were made, approvals were granted, and access was authorized. AI-powered deepfakes have quietly broken that model ...

Cloud migration was supposed to be a one-way door. For most enterprises, it turns out it isn't. Cloud data repatriation is a real and growing trend. A new survey ... finds that 89% of organizations plan to expand their on-premises infrastructure footprint over the next two years — and 75% have already moved at least some workloads back from public cloud in the past 24 months. The findings point to a broad rethinking of where data belongs ...

Over the past few years, large language models (LLMs) have revolutionized the software industry. Given their ability to excel at multi-step reasoning, LLMs have helped enterprises streamline workflows and adapt to the unknown. However, employing such models comes with sky-high costs, latency issues, and limited flexibility. In the realm of IT operations, it is generally wiser to employ smaller, domain-specific models instead ...

For years, DevOps teams operated under a simple assumption: collect enough telemetry, and you can find and fix any problem. That assumption is breaking down. Modern enterprises now operate across microservices, hybrid cloud environments, APIs, Kubernetes, and highly automated delivery pipelines. Releases happen continuously, dependencies shift constantly, and failures spread faster than teams can diagnose them ...

New Relic surveyed IT and engineering leaders from the media and entertainment (M&E) sector to understand what's working — and where challenges persist with their observability practices. The findings reveal how M&E organizations are navigating rising platform complexity, audience expectations, and AI-driven change. Below are five takeaways that stand out ...

Let me start with something I've seen play out more times than I can count. A team hits a wall with the cloud. Costs creep up, then spike. Performance starts to feel inconsistent. Someone in finance asks a simple question like "why did this double?" and nobody has a clean answer ... Maybe this isn't the right place for everything. That realization feels like a breakthrough, like you've identified the problem. In reality, you've just identified the starting line ...

In MEAN TIME TO INSIGHT Episode 24, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network observability tool sprawl ... 

In cloud-native systems, scaling is often as simple as moving a slider. For on-premise databases, the stakes are different. Over-provisioning hardware is expensive. Under-provisioning leads to performance bottlenecks that are difficult to fix once the equipment is in the rack ...

Elastic Adds Native Prometheus and PromQL Support to Elastic Observability

Unify Prometheus metrics with logs and traces, without rewriting queries or rebuilding pipelines

Elastic announced native Prometheus support, including direct ingestion via Remote Write and full PromQL support in Kibana.

These additions enable Site Reliability Engineers (SREs) to analyze Prometheus metrics alongside logs and traces in a single platform, without rewriting queries or rebuilding pipelines.

As organizations scale Kubernetes, Prometheus telemetry cardinality and volumes surge, forcing SREs to juggle multiple tools, duplicate data pipelines, and rewrite queries across systems. This fragmentation slows incident response and drives up operational costs.

With native Prometheus support, Elastic eliminates these fragmentation trade-offs by allowing teams to ingest, store, and analyze native Prometheus data alongside other telemetry data, while preserving existing Prometheus workflows. Instead of stitching together tools, SREs can detect, investigate, and resolve incidents end-to-end across AI and cloud-native environments faster and with less operational overhead.

“Modern incident response is slowed down by tool sprawl and disconnected data, and SREs shouldn’t have to pivot between tools or rewrite queries just to understand what’s happening in production,” said Bahaaldine Azarmi, general manager, Observability at Elastic. “With native Prometheus ingestion and PromQL in Kibana, teams get a single platform that dramatically reduces time to root cause.”

Native Prometheus Ingestion—No Translation Required (tech preview)

Elastic now ingests Prometheus metrics directly via Remote Write, eliminating the need for adapters, schema, or format translations.

SREs can stream Prometheus metrics straight into Elasticsearch while maintaining their original structure and semantics. The result is a single source of truth for observability, without forcing teams to abandon Prometheus. This approach:

  • Removes duplicate storage and pipeline complexity
  • Preserves full metric fidelity and high-cardinality data
  • Enables unified analysis across metrics, logs, and traces

Run PromQL Directly in Kibana (tech preview)

With native PromQL support in Kibana, users can run existing PromQL queries in dashboards and alerts without modification, lowering the barrier to adoption for teams already using Prometheus.

This eliminates query rewrites, one of the biggest adoption barriers in observability platforms. SREs can keep the PromQL they’ve already built, including dashboards, alerts, and workflows, alongside logs and traces in the same environment, while gaining a path from alert to root cause without manual pivoting, enabling deeper, cross-signal analysis during incidents.

Availability

Native Prometheus ingestion and PromQL support in Kibana are available in technical preview.
 

The Latest

I've spent a lot of time in the channel, and one thing I keep coming back to is this: a partner program is only as good as what it looks like in the field. Many programs look great on paper, but when a partner is in front of a customer navigating a complex hybrid environment or trying to make the case for AI-powered observability, the gap between what a vendor promises and what it actually delivers becomes very clear, very fast ...

Enterprises today operate in a real-time environment where uninterrupted access to trusted data has become a baseline expectation for users, applications and automated systems. Traditional DataOps models, built on manual effort and human triage, cannot keep pace with this always active demand. AI agents are emerging as the operational backbone, ensuring consistent data availability, reinforcing trustworthiness and enabling a level of scale that manual processes cannot achieve ...

For decades, trust in the digital workplace rested on familiar signals. We trusted faces on video calls, voices on the phone, and emails that appeared to come from people we knew. These cues felt human and intuitive. They anchored how decisions were made, approvals were granted, and access was authorized. AI-powered deepfakes have quietly broken that model ...

Cloud migration was supposed to be a one-way door. For most enterprises, it turns out it isn't. Cloud data repatriation is a real and growing trend. A new survey ... finds that 89% of organizations plan to expand their on-premises infrastructure footprint over the next two years — and 75% have already moved at least some workloads back from public cloud in the past 24 months. The findings point to a broad rethinking of where data belongs ...

Over the past few years, large language models (LLMs) have revolutionized the software industry. Given their ability to excel at multi-step reasoning, LLMs have helped enterprises streamline workflows and adapt to the unknown. However, employing such models comes with sky-high costs, latency issues, and limited flexibility. In the realm of IT operations, it is generally wiser to employ smaller, domain-specific models instead ...

For years, DevOps teams operated under a simple assumption: collect enough telemetry, and you can find and fix any problem. That assumption is breaking down. Modern enterprises now operate across microservices, hybrid cloud environments, APIs, Kubernetes, and highly automated delivery pipelines. Releases happen continuously, dependencies shift constantly, and failures spread faster than teams can diagnose them ...

New Relic surveyed IT and engineering leaders from the media and entertainment (M&E) sector to understand what's working — and where challenges persist with their observability practices. The findings reveal how M&E organizations are navigating rising platform complexity, audience expectations, and AI-driven change. Below are five takeaways that stand out ...

Let me start with something I've seen play out more times than I can count. A team hits a wall with the cloud. Costs creep up, then spike. Performance starts to feel inconsistent. Someone in finance asks a simple question like "why did this double?" and nobody has a clean answer ... Maybe this isn't the right place for everything. That realization feels like a breakthrough, like you've identified the problem. In reality, you've just identified the starting line ...

In MEAN TIME TO INSIGHT Episode 24, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network observability tool sprawl ... 

In cloud-native systems, scaling is often as simple as moving a slider. For on-premise databases, the stakes are different. Over-provisioning hardware is expensive. Under-provisioning leads to performance bottlenecks that are difficult to fix once the equipment is in the rack ...