TwitsBlog Show me a man who lives alone and has a perpetually clean kitchen, and 8 times out of 9 I'll show you a man with detestable spiritual qualities.
Ah, that is your local Nagios Log Server instance checking the status of elasticsearch/logstash to ensure that they're still running. These checks are generated to display the 'system status' properly.
2015-06-16 14_26_43-Home • Nagios Log Server - Firefox Developer Edition.png
You do not have the required permissions to view the files attached to this post.
TwitsBlog Show me a man who lives alone and has a perpetually clean kitchen, and 8 times out of 9 I'll show you a man with detestable spiritual qualities.
Yah, I saw those checks in our logs and wondered - what does NLS do if the status come back as not running? I haven't experimented with this, but is there some sort of notification we can do? Like, aim it at Nagios as a passive check result?
Currently NLS will display a red warning stating that logstash/elasticsearch aren't running, but currently it doesn't extend beyond that. We're open to suggestions though!
TwitsBlog Show me a man who lives alone and has a perpetually clean kitchen, and 8 times out of 9 I'll show you a man with detestable spiritual qualities.
Would love to be able to drop in an alert, similar to the alert logic for what happens when search results hit thresholds in NLS. Or maybe an event handler type thing where we get to put in the command line that gets executed when the thing is down?