When having multiple critical, only 1 is shown with check_openshift_es_stats

First of all thank you for this plugin for elasticsearch, we'll use it for elasticsearch in general since it has exact the functionality we're looking for.

We just noticed 1 thing (just a test in this case):

/usr/lib64/nagios/plugins/check_openshift_es_stats --endpoint http://127.0.0.1:9200 --jvm-heap-used-percent-critical 20 --total-jvm-heap-used-percent-critical 20 --fs-used-percent-critical 1

All three are critical, but the plugin outputs only 1 as criticial.

Example:

STATSQUERY CRITICAL - fs-used-percent-CtOHZDU is 66% (outside range 0:10) | 'fs-available-CtOHZDU'=13367MB;;;0;40188 'fs-available-percent-CtOHZDU'=34.0%;;;0;100 'fs-used-CtOHZDU'=26821MB;;;0;40188 'fs-used-percent-CtOHZDU'=66%;;10;0;100 'jvm-gc-collector-old-collection-count-CtOHZDU'=2;;;0 'jvm-gc-collector-old-collection-time-CtOHZDU'=0s;;;0 'jvm-gc-collector-old-collection-time-avg-CtOHZDU'=0.0445s;;;0 'jvm-gc-collector-old-collection-time-percent-CtOHZDU'=1e-05%;;;0;100 'jvm-gc-collector-young-collection-count-CtOHZDU'=2719;;;0 'jvm-gc-collector-young-collection-time-CtOHZDU'=15s;;;0 'jvm-gc-collector-young-collection-time-avg-CtOHZDU'=0.00567s;;;0 'jvm-gc-collector-young-collection-time-percent-CtOHZDU'=0.00159%;;;0;100 'jvm-heap-available-CtOHZDU'=427MB;;;0;990 'jvm-heap-available-percent-CtOHZDU'=44.0%;;;0;100 'jvm-heap-used-CtOHZDU'=563MB;;;0;990 'jvm-heap-used-percent-CtOHZDU'=56%;;20;0;100 'jvm-non-heap-used-CtOHZDU'=154MB;;;0 'node-fs-available-max'=13367MB;;;0 'node-fs-available-min'=13367MB;;;0 'node-fs-available-percent-max'=34.0%;;;0;100 'node-fs-available-percent-min'=34.0%;;;0;100 'node-fs-used-max'=26821MB;;;0 'node-fs-used-min'=26821MB;;;0 'node-fs-used-percent-max'=66%;;;0;100 'node-fs-used-percent-min'=66%;;;0;100 'node-jvm-heap-available-max'=427MB;;;0 'node-jvm-heap-available-min'=427MB;;;0 'node-jvm-heap-available-percent-max'=44.0%;;;0;100 'node-jvm-heap-available-percent-min'=44.0%;;;0;100 'node-jvm-heap-used-max'=563MB;;;0 'node-jvm-heap-used-min'=563MB;;;0 'node-jvm-heap-used-percent-max'=56%;;;0;100 'node-jvm-heap-used-percent-min'=56%;;;0;100 'process-cpu-percent-CtOHZDU'=0%;;;0 'total-fs-available'=13367MB;;;0;40188 'total-fs-available-percent'=33%;;;0;100 'total-fs-used'=26821MB;;;0;40188 'total-fs-used-percent'=66%;;;0;100 'total-jvm-heap-available'=427MB;;;0;990 'total-jvm-heap-available-percent'=43%;;;0;100 'total-jvm-heap-used'=563MB;;;0;990 'total-jvm-heap-used-percent'=56%;;20;0;100

It should also notify about the heap in this case, but it doesn't seem to.

Probably easy to solve ? Or isn't this plugin made to be used like this? :/ :)

[hansmi]

It's an effect of how the nagiosplugin module selects and formats the summary. The vshn_npo.nagiosutils.FullSummary class always outputs all metrics of the most significant status (e.g. all critical).