Nagios Support Forum

I think the wizard should indicate to the user the string match is going to be REGEX. If you use a literal such as mine, running(2), it will not match because of the parens being REGEX special characters

Dave

Excellent! The regex search works great for multiple good matches I just made it match running(2) or standby(7) ".*\((2|7)\)"

Thanks,

Dave

I am testing with 2026R1.5. Yes, if I change the type to string I can specify running(2) as the match and it should come up OK. This doesn't help with multiple "good" status options like running(2) or standby(7). Also I just did this with 2026R1.5 and it looks like it wrote the config chec...

I can do this with my own scripts but was wondering if one of the SNMP monitoring wizards would simplify this. I have Juniper switch gear and I'm trying to monitor the state of components like fan, Power supplies... This MIB has the information https://oidref.com/1.3.6.1.4.1.2636.3.1.13.1 snmpwalk -...

Ok, yesterday.... that error "Unable To Connect with SNMP, check credentials and try again." was coming up in red in the GUI next to the cancel/submit buttons when I clicked submit so no job was submitted to review. Today everything is working just fine so go figure.

Thanks,

Dave

Upgraded to 2026R1.5 and I"m trying out the SNMP walk monitoring wizard. Trying to setup a new walk job. It is a V3 run with authpriv and I've entered the same creds/settings that work from the Linux command line of the Nagios server. Keep getting error "Unable To Connect with SNMP, check ...

Using core config manager i have configured a service with a check command. The ARG1 value is a custom variable which is defined in a template for the service. This works in production, but testing the command with the "Run Check Command" button does not work. Seems like the variables from...

Also it seems the match type of numeric is not appropriate for an operating state value such as running(2). Can't set a threshold for that. But if I try changing match value to string it doesn't change the thresholds field format. Seems like I would need a match type that listed good, warning, criti...

So following this fix I ran the same job and it does show a selection table of 261 OIDs but it gives this boatload of errors first: warning Invalid warning numeric range for OID (jnxOperatingContentsIndex.1.1.0.0) warning Invalid critical numeric range for OID (jnxOperatingContentsIndex.1.1.0.0) war...

The log file looks pretty straightforward. attached No OIDs show up in the selection tables.

Dave