Metrics, Logs and Traces on One Platform

Felix Roessel

Principal Solutions Architect

Elastic

With AI-assisted root cause analysis, without giving up Grafana or PromQL

Two stacks, two bills, double the complexity? In this demo, we show you how to consolidate your backend, drastically reduce MTTR, and keep your SRE teams in their familiar workflows.

Tool silos slow down your root cause analysis

Many teams run Prometheus and Grafana for metrics and a second tool for logs. The everyday consequences:

• Inefficient troubleshooting: Linking metrics and logs across tool boundaries costs valuable minutes during outages.
• Double the effort & cost: Two platforms mean two bills, double the operations and higher token costs for AI analysis.
• Resistance from SREs: Tool changes often fail because teams don’t want to give up their familiar dashboards and queries.

THE SOLUTION: CONSOLIDATION WITHOUT DISRUPTION

You keep Grafana and PromQL while reducing infrastructure effort and costs.

What you’ll see in the demo:

• Keep Grafana, consolidate the backend: Connect Prometheus to Elasticsearch via remote_write. Grafana accesses it directly, so SREs keep working as usual.
• One stack for metrics, logs & traces: Everything on one central platform with Kibana, ES|QL, automatic anomaly detection and agent-based AI for root cause analysis (RCA).
• Higher performance, lower MTTR: Faster queries and direct data correlation significantly cut resolution time.

WHO IS THIS DEMO RELEVANT FOR?

This demo is aimed at engineering teams and architects who:

• Already work with Prometheus & Grafana but run a separate log tool.
• Want to simplify their observability landscape without retraining SREs.
• Want to use AI-assisted root cause analysis to reduce MTTR.