Notifications on errors from SNTP Traps

Hello,

Thank you for the KB-Post. It comes down to the architecture of PRTG. Which is based on numeric values on sensors. This is always the base of all sensors. This included such sensors like Trap & Syslog. The string-comparison, to check for certain traps, is first check for the sensor (or a filter you could say). Underneath the sensor has to count messages then, because it's our base architecture.
Thus, you can of course define a filter which will only allow very specific single traps to be counted for a sensor. The alerting will still base on a speed (traps per second). That can't be by-passed I'm afraid. So the key is, having the filter setup so that the sensor only sees those specific single traps.

best regards.

Hello, Torsten, Thank you for the clarification. Does it mean that we cannot set up our notification triggered by an event of "When Errors channel is Above 0 /second for at least 5 seconds perform some notification" so that it contained the info from that first trap which triggers the event? For example, an email with subject containing the string with error sent in that trap. Because, currently our emails' subjects and SMSs look like "(SNMP Trap Receiver) Speed reached (Errors) (>0 #/s) (OK)" and the real event can be found only in the email body.

Yes, that't right. Because of the limit, which is necessary to trigger the alert/notification, the actual sensor message will be that the limit was reached. And PRTG then can only supply Trap / Syslog messages as the mail body.