Dynamic SNMP OID workaround.
Hello fellow Zabbix enthusiasts.
I am currently setting up monitoring on some hosts and are having a hard time making this work.
We have a bunch of devices (about 5-800 per hosts) that needs operational status monitoring. The identification of these devices are done by SNMP OID and returns a serial number. This is the unique identifier we need. Since these devices can change ports we need to be able to track historical data across different SNMP OIDs, identified by the serial number.
I am thinking of two ways to do this. Either using scripts in Zabbix instead of SNMP Agent for discovery that creates the items needed and updates the items SNMP OID when a conflict (duplicate serial number) occurs.
Or to create the items needed using the regular SNMP Agent walk and then create some sort of database/table externally that keeps track of the serial numbers so that they can match when the items run.
Is there a better way to accomplish this? Am I overthinking this?
Thanks in advance,
Gabe
I am currently setting up monitoring on some hosts and are having a hard time making this work.
We have a bunch of devices (about 5-800 per hosts) that needs operational status monitoring. The identification of these devices are done by SNMP OID and returns a serial number. This is the unique identifier we need. Since these devices can change ports we need to be able to track historical data across different SNMP OIDs, identified by the serial number.
I am thinking of two ways to do this. Either using scripts in Zabbix instead of SNMP Agent for discovery that creates the items needed and updates the items SNMP OID when a conflict (duplicate serial number) occurs.
Or to create the items needed using the regular SNMP Agent walk and then create some sort of database/table externally that keeps track of the serial numbers so that they can match when the items run.
Is there a better way to accomplish this? Am I overthinking this?
Thanks in advance,
Gabe