I have a general (newbie) polling configuration question. Currently I've a functional setup monitoring the exit status of a net-snmp extend script using the OID of NET-SNMP-EXTEND-MIB::nsExtendResult."staleNFS" which contains the exit
status of the script.
The poller-configuration.xml entry, testing for a non-zero exit status is:
and when an outage occurs, the Minor Event text that is nicely displayed is:
staleNFS outage identified on interface 126.96.36.199 with reason code: Observed value '1' does not meet criteria '= 0'.
I am being requested by our users, (for easier triage) to grow this Reason message if possible, to include the STDOUT lines that my “extend” script returns, which are the paths to the actual NFS mounts that have an issue. The desired
string is available via the NET-SNMP-EXTEND-MIB::nsExtendOutputFull."staleNFS"
So my question is how is it best to configure this? Yes I could set up a second service detector and polling entry to test this additional OID for a non-empty string. Alternatively I could abandon the existing return status service completely
and use this second monitoring exclusively. Not thrilled about this one as I might get some false positives this way basing on STDOUT output of the script.
Is there an approach to augment the existing service/polling to solve this user request?
Thanks for reading this,
Note: Am not collecting this data for a Resource Graph generation as we’ve no need for it on this service.