ES|QL query patterns for Kibana Universal Alerting rules
Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability This functionality is generally available and ready for production usage. Serverless interfaces and procedures might differ from classic Elastic Stack deployments. The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability We plan to add this functionality in a future Elastic Stack update. Subject to changes. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
Serverless
Generally available
Stack
Planned
Planned
The following pages cover ES|QL query patterns for Kibana Universal Alerting rules, ordered from the simplest starting point to advanced use cases. Start with Your first rule query if you're new, or jump to the pattern you need.
| Pattern | What it solves | Complexity |
|---|---|---|
| Your first rule query | Alert on any individual event that matches a condition. No aggregation needed. | Beginner |
| Threshold queries | Alert when a metric crosses a limit. Covers single-series and grouped (per-host, per-service) rules. | Beginner |
| No-data detection | Alert when a specific host or data source stops reporting. | Intermediate |
| SLO burn rate | Alert when error budget consumption exceeds safe rates across multiple time windows. | Advanced |
| Persistent breach detection | Alert when a condition has been continuously true across consecutive time buckets. | Advanced |