Bugfix release 1.7.1 of monitoring plugin check_es_system

Written by - 0 comments

Published on April 1st 2020 - Listed in Monitoring Elasticsearch


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



Add a comment

Show form to leave a comment

Comments (newest first)

No comments yet.