Want this feature implemented, too? Please upvote by clicking Thumbs up!
(Posts as a reply won't be published in this feature request thread. Read Me!)
As a PRTG User, I want PRTG to provide complete SNMP trap management. PRTG is fantastic when it comes to reaching out into our network and looking for potential issues. But it is effectively tone deaf when our network tries to tell PRTG that something is wrong with itself.
Details of User Story
PRTG provides rudimentary SNMP trap handling that appears to be constrained by the one-size-fits-all framework for sensors that PRTG has been designed around. Consequently, its SNMP trap handling has at least two major shortcomings:
1. If a device reboots, PRTG generally won't pick up the coldStart SNMP trap because it has paused all of the device's sensors, including the SNMP trap sensor itself. This is a biggie. Of all the possible SNMP traps, this one is the most basic but can potentially convey critical implied information about a device's health, especially if it reboots when it wasn't meant to, or it reboots frequently. 2. SNMP traps are treated as transitory. They cause the sensor state to transition to Warning or Error on the next scan, but then it reverts back to OK on the following scan.
This second shortcoming means that the onus is on the PRTG administrator to configure email notifications for SNMP traps and then to manage the events from within their mailbox, not from within PRTG itself. Compare this with other network management solutions that offer complete SNMP trap event management, including pervasive alerts that must be acknowledged.
- PRTG successfully handles coldStart SNMP traps.
- PRTG treats non-informational SNMP traps as pervasive alerts that must be acknowledged rather than a transitory state change.