Setting up brand new cluster, and have configured metricbeat style monitoring of cluster (separate elasticsearch for monitoring).
Entered setup mode and did the add of standard alerts. Looks like these rules got created but am seeing Error status on all.
CCR read exceptions
CPU Usage
Cluster health
Disk Usage
Elasticsearch version mismatch
Kibana version mismatch
License expiration
Memory Usage (JVM)
Error that is shown for each....
search_phase_execution_exception: [illegal_argument_exception] Reason: no mapping found for cluster_uuid in order to collapse on; [illegal_argument_exception]
Hi, did reach out to support for guidance, and the root cause was that I'd done monitoring alert setup on the actual production Kibana... But instead I needed to setup Kibana on the dedicated monitor cluster. Makes sense I guess thinking about it.
Also I had to enable the nodes with role 'remote_cluster_client' to get things working fully.
All good now! Alerts setup with PagerDuty actions as well so we're cookin' with fire now.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.