Alerting and action settings in Kibana
editAlerting and action settings in Kibana
editAlerts and actions are enabled by default in Kibana, but require you configure the following in order to use them:
- Set up Kibana to work with Elastic Stack security features.
- Set up TLS encryption between Kibana and Elasticsearch.
-
If you are using an on-premises Elastic Stack deployment, specify a value for
xpack.encryptedSavedObjects.encryptionKey
.
You can configure the following settings in the kibana.yml
file.
General settings
edit
|
A string of 32 or more characters used to encrypt sensitive properties on alerts and actions before they’re stored in Elasticsearch. Third party credentials — such as the username and password used to connect to an SMTP service — are an example of encrypted properties. |
Action settings
editA list of hostnames that Kibana is allowed to connect to when built-in actions are triggered. It defaults to |
|
A list of action types that are enabled. It defaults to |
Alert settings
editYou do not need to configure any additional settings to use alerting in Kibana.