What I found from the code: In Opsview 3.5.1, if you configure a SNMP Polling check, you have the options 'equals' and 'regex' for String Comparison checks. 'regex' passes the option '-r' to check_snmp, 'equals' passes '-s' to check_snmp. Further, 'check_snmp -s STRING' returns OK if STRING is an exact match, so the description in the Opsview Service Check configuration (SNMP Polling, Critical comparison) should reflect that the Opsview check is CRITICAL if the string ist not matched, e.g. by changing the description to 'doesn't equal'.
On the other hand, my SNMP device returns '"OK"', i.e. including surrounding double qoutes. check_snmp doesn't strip qoutes, so I have to enter OK with qoutes for the string comparison value. -- kind regards, Henry On Mo, 2010-01-18 at 15:20 +0100, [email protected] wrote: > Dear Opsview users! > > I am configuring my first SNMP Polling check and can't find any > documentation on the "String Comparison" options: How to raise a > critical error if the SNMP query doesn't match a string, like > 'ciritcal if $query != "OK"'? I tried operators like '!=', 'neq', > 'ne', but none of them worked. > > I appreciate any clarification on SNMP Polling result matching. > _______________________________________________ Opsview-users mailing list [email protected] http://lists.opsview.org/lists/listinfo/opsview-users
