From alert to root cause in 3 minutes: automated root cause analysis with Elastic Agent Builder
Automated root cause analysis only works if the agent compares the incident window against the last healthy one. Skip that step and you get a summariser. The read-only skill, the scoped role and the Elastic Workflow are all here.
Elastic Agent now runs as an OpenTelemetry Collector: Less memory overhead, zero config changes
Elastic Agent 9.3 sends logs, metrics and traces through one OTel Collector pipeline, running Beats integrations alongside native OTel sources in a single Fleet-managed agent.
Android application monitoring with OpenTelemetry: distributed tracing from tap to backend
EDOT Android adds mobile APM to your Android app with one Gradle dependency: crash reporting, session tracking and distributed tracing visible in Kibana.
One edit, every dashboard updated: managing Kibana observability at scale with Terraform
Define your golden-signals panels once in a shared HCL library and use for_each to generate every team's dashboard, with drift detection and git rollback built in.
Elastic integrations come with alerting rule templates, each one an ES|QL query with a threshold already set. Create Elasticsearch alert rules in minutes, tune them to your traffic, and catch silent data streams early.
You have the IP, you want the hostname: building a lookup processor for OpenTelemetry
Look up any value from YAML, CSV or DNS inside the OpenTelemetry Collector or wire in your own source through a processor Elastic built and shipped to Collector Contrib.
Your SLO is on fire; here's how to find the arsonist in Elastic Observability
When SLO alerting flags a burn rate spike, follow the SLI from the alert detail page through bad event spans and trace waterfalls to find the exact dependency burning your SLO error budget, all without leaving the investigation.
6x faster at 500 services: how we rebuilt the Kibana APM service map from canvas to React DOM
Each service node shows alert, SLO and anomaly health so you can filter to breaching services only and embed the result on any Kibana dashboard, with full keyboard navigation across the topology.
Four clicks from alert to root cause: how Elastic Observability links APM services to Kubernetes infrastructure
Check service dependencies and compare per-pod CPU, memory and network trends on the Infrastructure tab to find which instance is causing trouble, all without leaving the alert investigation.
From alert to failing dependency in four clicks: Elastic APM's embedded service map
The APM service map is now embedded on alert pages with filters, connection metrics and a service fly-out so you can analyse dependencies and find the root cause without leaving the alert.
