Nagios Support Forum

Thanks for the information.

The plugins appear to implement a polling pattern (I.e., check_temp, check_snmp, check_uptime.) How do I handle a status that is pushed to me?

tmcdonald wrote:The exit code of 0 through 3 determines the OK, WARNING, CRITICAL, or UNKNOWN status

When you say "Exit code", you don't actually mean the plugin exits, do you?

coding the threshold inside the plugin doesn't seem like a good architecture We agree: There are a few reserved options that should not be used for other purposes: -V version (--version) -h help (--help) -t timeout (--timeout) -w warning threshold (--warning) -c critical threshold (--critical) -H h...

In addition to what tmcdonald posted: From http://nagios.sourceforge.net/docs/3_0/pluginapi.html : Plugin Output Spec At a minimum, plugins should return at least one of text output. Beginning with Nagios 3, plugins can optionally return multiple lines of output. Plugins may also return optional pe...

The exit code of 0 through 3 determines the OK, WARNING, CRITICAL, or UNKNOWN status. You can also pass back textual information, and information that will be used to graph (performance data): https://nagios-plugins.org/doc/guidelines.html Thanks. Graphing is something that I am interested in. Can ...

I have a system that implements a messaging middleware. I want to build a plugin for Nagios to capture status messages being sent across this middleware. The status messages can be very robust and include many parameters (E.g., State, mode, status, uptime, software revs, hardware info, installation ...