I'm not sure if this helps but here is a screenshot of the debug log file:
Thanks!
Status critical
Re: Status critical
Hi friends,
I've found a workaround for my issue, instead of using -r for the regex I'm using -c 1: which sets a threshold range that states that anything equals to 1 or bigger is OK while a 0 gives me a critical status (that's the behavior i wanted to achieve).
That still doesn't explain why the regex expression wouldn't work in the first place with the interface. I'm still curious as to why this is happening so I will keep the post open.
Any suggestions are welcome and thanks again for all the help.
I've found a workaround for my issue, instead of using -r for the regex I'm using -c 1: which sets a threshold range that states that anything equals to 1 or bigger is OK while a 0 gives me a critical status (that's the behavior i wanted to achieve).
That still doesn't explain why the regex expression wouldn't work in the first place with the interface. I'm still curious as to why this is happening so I will keep the post open.
Any suggestions are welcome and thanks again for all the help.
-
- Former Nagios Staff
- Posts: 4583
- Joined: Wed Sep 21, 2016 10:29 am
- Location: NoLo, Minneapolis, MN
- Contact:
Re: Status critical
Can you post your commands.cfg (or wherever you have your commands defined)?
Re: Status critical
Here is a print screen of the check_snmp command definition:
Thanks!
Thanks!
-
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: Status critical
I believe the -r is for matching sting values, but that OID returns an INTEGER32