Can we collect performance data history using SNMP Trap monitor?
Q: We have recently acquired temperature sensors capable of sending SNMP traps. How can we utilize SNMP Trap monitors to keep temperature historical data?
A: SNMP Trap monitors can’t be used to collect data periodically. IPNetwork Monitor normally polls monitors to collect and store historical data. SNMP Trap monitors are different, since they are not polled periodically, but triggered by the event sent by monitored device. SNMP Traps are useful if instant notification is required (for example, when monitored parameter exceeds acceptable range).
SNMP Custom monitors should be used to collect monitoring history, and SNMP
Traps should be used to generate alerts as quickly as possible.
In case you are looking for proper MIB for your device, you can start your search from network device’ vendor’s site.
Please refer to other SNMP-related articles in our Knowledge Base, in case you have encountered problems getting SNMP traps.
Related topics:
What typical SNMP monitors can be used for Linux servers?
How can I monitor SNMP-enabled devices with your application?
Check out our Knowledge Base where we answer questions regarding various topics. No. SNMP Trap monitors react to trap events from devices and are not polled periodically, so they are not suitable for collecting regular historical values. Use an SNMP Custom monitor when you need IPNetwork Monitor to poll a value regularly and store performance history. SNMP Traps are useful for immediate event notification, such as alerting as soon as a temperature sensor reports that a value exceeded an acceptable range.
Frequently Asked Questions
Can an SNMP Trap monitor store periodic temperature history?
Which monitor type should collect SNMP-based history?
When are SNMP Traps useful?