Alerting and action settings in Kibanaedit
Alerts 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 settingsedit
|
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 settingsedit
|
Feature toggle that enables Actions in Kibana.
If |
A 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 |
|
|
Specifies preconfigured action IDs and configs. Defaults to {}. |
Specifies the proxy URL to use, if using a proxy for actions. By default, no proxy is used. |
|
Specifies HTTP headers for the proxy, if using a proxy for actions. Defaults to {}. |
|
Set to |
|
Set to |
|
Specifies the max number of bytes of the http response for requests to external resources. Defaults to 1000000 (1MB). |
|
Specifies the time allowed for requests to external resources. Requests that take longer are aborted. The time is formatted as: |
Alert settingsedit
You do not need to configure any additional settings to use alerting in Kibana.