The Alerting feature is automatically enabled in Kibana, but might require some additional configuration.
If you are using an on-premises Elastic Stack deployment:
If you are using an on-premises Elastic Stack deployment with security:
- You must enable Transport Layer Security (TLS) for communication between Elasticsearch and Kibana. Kibana alerting uses API keys to secure background rule checks and actions, and API keys require TLS on the HTTP interface. A proxy will not suffice.
- If you have enabled TLS and are still unable to access Alerting, ensure that you have not explicitly disabled API keys.
Production considerations and scaling guidanceedit
When relying on alerting and actions as mission critical services, make sure you follow the Alerting production considerations.
See Scaling guidance for more information on the scalability of Kibana alerting.
To access alerting in a space, a user must have access to one of the following features:
See feature privileges for more information on configuring roles that provide access to these features.
Also note that a user will need
read privileges for the Actions and Connectors feature to attach actions to a rule or to edit a rule that has an action attached to it.
For security reasons you may wish to limit the extent to which Kibana can connect to external services. Action settings allows you to disable certain Connectors and allowlist the hostnames that Kibana can connect with.
Rules and connectors are isolated to the Kibana space in which they were created. A rule or connector created in one space will not be visible in another.
Rules are authorized using an API key associated with the last user to edit the rule. This API key captures a snapshot of the user’s privileges at the time of edit and is subsequently used to run all background tasks associated with the rule, including condition checks, like Elasticsearch queries, and action executions. The following rule actions will re-generate the API key:
- Creating a rule
- Enabling a disabled rule
- Updating a rule
If a rule requires certain privileges, such as index privileges, to run, and a user without those privileges updates, disables, or re-enables the rule, the rule will no longer function. Conversely, if a user with greater or administrator privileges modifies the rule, it will begin running with increased privileges.
If you want to use alerting rules with cross-cluster search, you must configure privileges for CCS and Kibana.