As we approach ten years of
icinga (2009-05-15), which started out as a fork of Nagios. Almost twenty years after the original NetSaint (1999), renamed Nagios in 2002. We have been using the same Plugin Return Codes for the last twenty years.
|Numeric Value||Service Status||Status Description|
||The plugin was able to check the service and it appeared to be functioning properly|
||The plugin was able to check the service, but it appeared to be above some “warning” threshold or did not appear to be working properly|
||The plugin detected that either the service was not running or it was above some “critical” threshold|
||Invalid command line arguments were supplied to the plugin or low-level failures internal to the plugin (such as unable to fork, or open a tcp socket) that prevent it from performing the specified operation. Higher-level errors (such as name resolution errors, socket timeouts, etc) are outside of the control of plugins and should generally NOT be reported as UNKNOWN states.|
POSIX return codes support
255, and we only use a few.
Do you think it’s time to support additional status codes?
I’m just interested in the opinion of the community.
- What’s a
- It’s long overdue
- I could use additional status codes
- If it ain’t broke, don’t fix it
- Who’s going to change all of the
- I don’t have an opinion
- Other (reply to topic)
For example: I use
check_users to see the number of users logged a system.
Critical could be considered too severe when a single user is logged in. Having
Minor status codes would be nice to have.