A new version of the check_es_system, a monitoring plugin to monitor Elasticsearch nodes or clusters, is available!
The new version 1.7.1 is a bugfix release and handles a problem when Elasticsearch would return a 503 error. Such a case may happen, if you run a load balancer or reverse proxy in front of Elasticsearch (as an example).
Prior to the bugfix, the plugin would return "garbage", because the 503 error was not caught and the plugin tried to parse the (non-existing) json output from Elasticsearch:
# /opt/check_es_system.sh -H localhost -P 9200 -t status -u user -p secret
json read error: line 1 column 1: '[' or '{' expected near '<'
json read error: line 1 column 1: '[' or '{' expected near '<'
json read error: line 1 column 1: '[' or '{' expected near '<'
json read error: line 1 column 1: '[' or '{' expected near '<'
json read error: line 1 column 1: '[' or '{' expected near '<'
json read error: line 1 column 1: '[' or '{' expected near '<'
json read error: line 1 column 1: '[' or '{' expected near '<'
json read error: line 1 column 1: '[' or '{' expected near '<'
In such a scenario, the plugin now returns:
# /opt/check_es_system.sh -H localhost -P 9200 -t status -u user -p secret
ES SYSTEM CRITICAL - Elasticsearch not available: localhost:9200 return error 503
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 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