check_logstash icon indicating copy to clipboard operation
check_logstash copied to clipboard

Icinga check plugin to check the status of Logstash

Results 16 check_logstash issues
Sort by recently updated
recently updated
newest added

Hi, we wanted to have extended features for this plugin for our use case, which includes: - Possibility to monitor only one single pipeline - Possibility to monitor the incoming/outgoing...

Hi Thomas, I noticed that the perfdata for the .events.out are counted. I currently have a very huge events.out count (1,399,787,534.00 :D ) Wouldn't it be better to calculate the...

Hi @widhalmt We have a logstash with several pipelines defined, where on the one side, some pipelines always have to get inflight events and on the other side, some only...

Hello, Logstash stats API has changed and out counter does not include anymore items discarded by a filter option so there is no more any way to known if in...

When comparing named pipelines, if there is a historical error, the service will show as critical even if it has successfully reloaded since then. This adds the same timestamp check...

Hello. I have issue using this plugin using custom alarms for inflight-events-warn and inflight-events-crit Here is the output without parameters: [root@coreinit check_logstash]# ./check_logstash -H localhost OK - Logstash seems to...

When you write the status like `[OK]` or `[WARNING]` in Icinga Web 2 2.7+ it gets highlighted automatically. No matter if this is part or a multiline output or not....

fix for reload error detection + verbose option

Since upgrading to ELK 6, I now get this from this plugin: ``` /usr/local/lib/nagios/plugins/check_logstash.rb:195:in `rescue in get': pipeline.events.out (CheckLogstash::Result::InvalidField) from /usr/local/lib/nagios/plugins/check_logstash.rb:187:in `get' from /usr/local/lib/nagios/plugins/check_logstash.rb:183:in `get' from /usr/local/lib/nagios/plugins/check_logstash.rb:388:in `inflight_events_health' from /usr/local/lib/nagios/plugins/check_logstash.rb:342:in...

In a feedback issue @jordansissel stated that alarming on open file descriptors is something that might not be wanted by every user. Since it is already implemented I changed it...

help wanted
question