Should the check_statuspage_components plugin report timeouts as UNKNOWN state?

[atc0005]

See #89 for details.

This GH issue is meant to address whether the problem should be reported as a CRITICAL state (current behavior), or if UNKNOWN is more appropriate.

[atc0005]

This GH issue is meant to address whether the problem should be reported as a CRITICAL state (current behavior), or if UNKNOWN is more appropriate.

I've gone around in circles on this topic before and keep coming back to this entry in the "Plugin Return Codes" section of the plugin dev guidelines:

Numeric Value	Service Status	Status Description
3	Unknown	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.

Specifically this admonition:

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.

refs https://nagios-plugins.org/doc/guidelines.html#AEN78