Configure Stack monitoring alerts
editConfigure Stack monitoring alerts
editYou can configure Stack monitoring alerts to be sent to you by email when health related events occur in your deployments. To set up email notifications:
- Enable logging and monitoring on deployments for which you want to receive notifications. You need to enable only metrics data being shipped for the notifications to work.
-
In Kibana, configure the email connector to send email from Elastic Cloud. If you want to use the preconfigured
Elastic-Cloud-SMTP
connector in Elastic Cloud, then you can skip this step. - From the Kibana main menu, go to Stack Monitoring. On this page you can find a summary of monitoring metrics for your deployment as well as any alerts.
- Select Enter setup mode.
-
On any card showing available alerts, select the alerts indicator. Use the menu to select the type of alert for which you’d like to be notified. There are many alert types, including:
- CPU usage threshold
- Disk usage threshold
- JVM memory threshold
- Missing monitoring data
- Thread pool rejections (search/write)
- CCR read exceptions
- Large shard size
-
Cluster alerting, including:
- Elasticsearch cluster health status
- Elasticsearch, Kibana, or Logstash version mismatches
- Elasticsearch nodes changed
All of these alerts are described in detail in Kibana alerts. Check the documentation matching your Kibana version to find which alerts are available in that release.
For the
Elasticsearch nodes changed
alert, if you have only one master node in your cluster, during the master node vacate no notification will be sent. Kibana needs to communicate with the master node in order to send a notification. One way to avoid this is by shipping your deployment metrics to a dedicated monitoring cluster, which you can configure when you enable logging and monitoring in Step 2. - In the Edit rule pane, set how often to check for the condition and how often to send notifications.
-
In the Actions section, select Email as a connector type and select the email connector that you configured in Step 3 (or the preconfigured
Elastic-Cloud-SMTP
connector). - Configure the email contents and select Save. Make sure that the email address you specify is the one that you allowed in Step 1.