A new version of check_es_system, a plugin to monitor ElasticSearch nodes or clusters, is available.
The new version 1.5.1 fixes a bug in the "status" check type. It now catches when the cluster health url would not be reachable or would show no output.
Without the bugfix, the plugin would silently fail but would still return an exit code 0 (resulting in OK in the monitoring application):
# /usr/lib/nagios/plugins/check_es_system.sh -H myESnode -u monitoring -p secret -t status
parse error: type 'object' has no elements to extract (arg 2)
json read error: line 2 column 0: '[' or '{' expected near end of file
json read error: line 2 column 0: '[' or '{' expected near end of file
json read error: line 2 column 0: '[' or '{' expected near end of file
This was caused when the cluster health page (/cluster/health) returned no data. In this particular case it was a full cluster failure leading to this.
With 1.5.1 this now works correctly:
# /usr/lib/nagios/plugins/check_es_system.sh -H myESnode -u monitoring -p secret -t status
ES SYSTEM CRITICAL - unable to get cluster health information
No comments yet.
AWS Android Ansible Apache Apple Atlassian BSD Backup Bash Bluecoat CMS Chef Cloud Coding Consul Containers CouchDB DB DNS Database Databases Docker ELK Elasticsearch Filebeat FreeBSD Galera Git GlusterFS Grafana Graphics HAProxy HTML Hacks Hardware Icinga Influx Internet Java KVM Kibana Kodi Kubernetes LVM LXC Linux Logstash Mac Macintosh Mail MariaDB Minio MongoDB Monitoring Multimedia MySQL NFS Nagios Network Nginx OSSEC OTRS Office OpenSearch PGSQL PHP Perl Personal PostgreSQL Postgres PowerDNS Proxmox Proxy Python Rancher Rant Redis Roundcube SSL Samba Seafile Security Shell SmartOS Solaris Surveillance Systemd TLS Tomcat Ubuntu Unix VMWare VMware Varnish Virtualization Windows Wireless Wordpress Wyse ZFS Zoneminder