Following the Elasticsearch cluster issues in our ELK stack (mentioned in the previous article Docker logging with GELF using tcp: The good, the bad, the ugly), I got aware that the monitoring plugin check_es_system didn't correctly alert, when ElasticSearch was down on a node.
Today's release is a double-release with two independent improvements.
Version 1.2 fixes issue 6 by verifying that the "-t" (checktype) parameter was defined, which is a mandatory parameter.
Version 1.3 fixes issue 8 (Catch connection refused error). This is actually something essential every monitoring plugin which opens a remote connection should do.
The plugin now correctly throws a CRITICAL error, when the connection cannot be established:
# ./check_es_system.sh -H es02.example.com -t status -u elastic -p secretpass
ES SYSTEM CRITICAL - Failed to connect to es02.example.com port 9200: Connection refused
No comments yet.
AWS Android Ansible Apache Apple Atlassian Automation BSD Backup Bash Bluecoat CMS Chef Cloud Consul Container Containers CouchDB DB DNS Database Databases Docker ELK ElasticSearch Elasticsearch Filebeat FreeBSD GlusterFS Grafana Graphics HAProxy HTML Hacks Hardware Icinga Icingaweb2 InfluxDB Internet Java Kibana Kubernetes LXC Linux Logstash Mac Macintosh Mail MariaDB Minio MongoDB Monitoring Multimedia MySQL NFS Nagios Network Nginx OSSEC OTRS PGSQL PHP Perl Personal PostgreSQL Postgres PowerDNS Proxmox Proxy Rancher SSL Security Shell SmartOS Solaris Surveillance SystemD TLS Tomcat Ubuntu Unix VMWare VMware Varnish Virtualization Windows Wireless Wordpress Wyse ZFS Zoneminder