Type to search.

Notifications and actions in Kibana Universal Alerting

Serverless

Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud.

Availability

  • Generally available

    This functionality is generally available and ready for production usage.

Serverless interfaces and procedures might differ from classic Elastic Stack deployments.

Stack Planned

The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats.

Availability

  • Planned

    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.

To notify people or run automation for an alert in Kibana Universal Alerting, build a workflow and create an action policy that invokes it. Action policies act only on alerts, so the rule's mode must be Detect and respond or Alert (depending on your Elastic Stack version).

Note

To use workflows, your role must have the appropriate privileges and your subscription must include workflows. Refer to the subscription page for Elastic Cloud and Elastic Stack/self-managed for a breakdown of available features by tier.

To send a notification or trigger an action from a rule in Kibana Universal Alerting:

  1. Build a workflow that defines what to do, for example, send a message, call a webhook, open a case, or run any other automation.

  2. Create an action policy that routes alerts to that workflow. The action policy controls which alerts qualify, how they batch, and how often it invokes the workflow.

    To apply the policy to specific rules, give the policy and those rules the same routing tag.

    To run a workflow when a user acts on an alert, such as opening a ticket when someone assigns it, use an alert lifecycle trigger instead. For a comparison, refer to Connect workflows.