Open wols opened 6 years ago
I'm not sure how we handle no longer supported plugins. There is always the case of someone using this plugin and us breaking their setup by removing the CheckCommand.
If someone finds an alternative implementation/plugin, we can deprecate the current one. For now, thanks for the note but honestly I have no idea what our actions should be ...
Hi all, I use this plugin: https://github.com/orthecreedence/check_elasticsearch
Actually it doesn't look so inferior, but four out of a total of 6 arguments of the current plugin would not work with this alternative.
elasticsearch_failuredomain
, elasticsearch_masternodes
and elasticsearch_prefix
can't be used with the alternative plugin, because the plugin does not offer it at all.elasticsearch_yellowcritical
of the current plugin, the alternative plugin has a suitable parameter though is meant for the complete opposite of what the current plugin offers. In particular, it can be used to treat the cluster warning state as OK
.
[...]
echo " -k/--ok-on-yellow)"
echo " Exit with OK state if the cluster is yellow."
[...]
https://www.claudiokuenzler.com/monitoring-plugins/check_es_system.php
This would be also a good alternative and is up-to date with much more options than what we are already using. But since I don't ever/use Elasticsearch, I can't say what is the best for you all, so maybe we should ask in the community form instead.
The config... https://github.com/Icinga/icinga2/blob/83ad98420a28e1af18145f8bbac5a945881c3a78/itl/plugins-contrib.d/databases.conf#L713 ...refers to a not maintained plugin anchor/nagios-plugin-elasticsearch/issues/48
Of topic: A other simple HTTP-based check is described here: https://stackoverflow.com/questions/10276989/how-to-monitor-elasticsearch-using-nagios