first of all what do you want to montitor? Speical hardware? Do you want to check active or you want to receive SNMP Traps? Both it a a little bit difficult to automate. That means, that somebody has to maintain how the OID and the value is to translate or to handle. Above all, what should be queried for the respective hardware. Every vendor has it’s own MIB list which you have to download for your hardware and import it in your prefered tool or script. There are some standard OIDs every vender can use. e.g. uptime. There are a lot of MIB databases in the web, where you can see or download these information. But the ones I know are not completely. Some of the OIDs you only get only from your vendor.
For example: Take a look in the nwc_health check. If you check the source, you’ll wee that the author included every OID and in the source code for the network devices and how to handle with the value. After compiling you have one script with all the OIDs and a very very long script.
So what you can do, if you don’t want not to program your own script, is to use existing scripts like nwc_health_check for network devices or use programs, they have already included the MIBs or use scripts/programs where you can import the MIBs from your vendor.
Yes you could do a snmpwalk on every device. But depending how many information you can catch from your device it may needs time. And then you have again the problem to translate the OIDs and values to human readable values. Or do you know without to google that 184.108.40.206.220.127.116.11 is the already mentioned sysuptime?
For your question how we handle that:
we are using existing script where the required OIDs are already included. If not, we have to use the check snmp from the ITL with the OID we want to check.
For traps we use logstash and I created our own translation list. Because The snmp-plugin want to have the files in the yaml-format. And I never found a working tool to translae the mib files from the vendor into the yaml format.
At the OSMC I talked with a community member about this. He is working in a company where his colleague wrote their own snmp tool!