Nagios Support Forum

If you can, yes. I'm actually getting asked for that a lot these days from the people in my organization.

It seems easy enough to set up a threshold number, but is it possible to set up a per-host threshold alert, without setting up a separate alert for each host?

Is there a way to generate an alert when we haven't received logs from a log source, say, in the last hour or so? Without setting up a specific alert for each individual server? Just looking for a way to detect if a server's syslog or nxlog process died or something.

Just want to check before I update, to find out if the following patch has been included in the ua_parser version that the latest Nagios Log server (2.1.9) is using. The one we're currently using (2.1.7) is not, but I don't update often (if it ain't broke, etc etc). https://github.com/ua-parser/uap-...

Will Nagios eventually update the version of Elastic included with the log server? Right now it's on 1.7.6 and the official Elastic is way beyond that (6.x using the Apache license).

Just FYI, restarting logstash didn't work. This wouldn't be a big deal except I have to go tweak one of the filters. Damn good thing I took a backup of the config files, but I do have quite a bit of custom stuff in there. Guess I'd better get started.

This is a little wierd. Looks like the log server's config pages are completely empty. Global Config View: # # Logstash Configuration File # Dynamically created by Nagios Log Server # # DO NOT EDIT THIS FILE. IT WILL BE OVERWRITTEN. # # Created Thu, 22 Mar 2018 15:21:18 -0400 # # # Global inputs # #...

I'm collecting some Apache logs in a custom format, and I'm pulling the HTTP response as an integer to avoid any wierdness. The thing is, I can't seem to display this in a terms chart of any sort. Is there a way to get the panel to treat this as a string for display purposes?

I could swear I had edited that to say netlog3 and use the next port in sequence. I'll make the change and keep an eye on it. We're using these three ports for syslogging from network devices, and Cisco doesn't follow the syslog standard so I had to roll my own filter for some of this stuff.

Once every 3 or 4 days. ps -ef|grep java nagios 2553 1 36 Feb20 ? 2-10:46:54 java -Xms128837m -Xmx128837m -Djava.awt.headless=true -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -XX:+HeapDumpOnOutOfMemoryError -XX:+DisableExplicitGC ...