This alert will trigger when the JVM Heap utilization of an Elasticsearch cluster node is >90%.

This alert triggers when the reported health of an Elasticsearch index is 'red'.

This alert is triggered when the count of active queries on primary shards deviates more than 2 standard deviations above or below the baseline.
This can be a leading indicator of a potential loss of service or flood of requests.

This alert will trigger when the Flush latency for an Elasticsearch cluster's primary shards is >5ms.
This is measured by: # of Flushes / Time spent on Flushes (ms) for the evaluated time window.
Increased Flush Latency is an indication that your disks cannot keep up with your cluster's demands and you may need to reconfigure the 'flush_threshold_size' setting to reduce the translog size needed to trigger a flush operation.

This alert will trigger when the Indexing latency for an Elasticsearch cluster's primary shards is >5ms.
This is measured by: # of Docs Indexed / Time spent Indexing (ms) for the evaluated time window.
Increased Flush Latency is an indication that you are trying to index too many documents at one time and you may need to reconfigured your settings to increase performance.

This alert triggers when the reported health of an Elasticsearch cluster is 'red'.

This alert will trigger when the File Store of an Elasticsearch cluster node is >90% full.