If you supply a few of the SNMP OIDs, we will have a much better idea of what you are trying to achieve.
Simple leaf OIDs contain a single piece of data, other are table based and are a little more complex.
Once we have the collection setup we can take you through the alerting.
You can string together multiple conditions for multiple Row IDs. Check out the Custom Table Poller Current Status example:
For your use case, OR would be appropriate for first drop down. Note the 'plus' symbol which allows you to add additional conditions (additional Row IDs).
Same issue here. I finally got some visibility into the hardware health of my supermicro servers, but I've hit a snag getting an alert to trigger based on the data polled. I'm trying to alert on PSU Status and temperature . In this case, it would be the Reading value not equaling a certain value.
OID - 220.127.116.11.4.1.10818.104.22.168.1.1.4
Above you elude to setting the ROW ID to a specific # but where do I capture that Row ID #?
So yes, i did use multiple Row's and I se the conditions to match the current values... just to test of the logic would trigger. I matched the Row's to the actual text displayed on the Web page field, case sensitive. In your screenshot, i see a Row #, almost like an SQL table perhaps. Is that where you got that from?
The goal here is to make this a scalable solution. We will be deploying thousands of these servers. So I cannot go back and tweak alerts and OID's for each node. I need a solution that I can configure once for many servers.
I cant seem to attach the SNMP crawl here, but if I had to guess, the OID with the actual data I want to alert on is below
Dropbox - X10 crawl.txt
OID being polled - 22.214.171.124.4.1.108126.96.36.199.188.8.131.52.x
I think this is the specific OID for PS2 Status - 184.108.40.206.4.1.108220.127.116.11.18.104.22.168 = INTEGER: 0
Thanks for the help