Rules in Kibana Universal Alerting
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
Looking for Kibana Classic Alerting? Refer to the Kibana Classic Alerting overview.
In Kibana Universal Alerting, a rule is where detection starts. It points Kibana at the data you care about, describes what counts as a problem in ES|QL, and says how often to check. On each scheduled run, Kibana writes each matching row as a rule event to .rule-events. Those events are never overwritten.
A rule doesn't send notifications. Action policies match alerts from any rule and invoke a workflow, which sends the notification. You can change how policies route alerts without changing a rule's detection logic, and several policies can respond to the same alert independently.
- Create a rule: Compare creation paths and select the one that fits your workflow.
- Configure a rule: Set the schedule, grouping, alert delay, recovery condition, and no-data behavior.
- Rule mode: Set whether matches are grouped into an alert or remain available for later analysis.
- View and manage rules: Enable, disable, clone, delete, and bulk-manage rules from the Rules page.