Filtering of SNMP Trap Receiver doesn't seem to work

Modified on 2025-06-10 14:02:25 +0200

Hello,

I have set up the snmp trap receiver sensor. The traps are received by the sensor, it shows the value from the configured OID, but it seems that the sensor is ignoring the "Benutzerdefinierter Trapcode" option. Neither a "real" trapcode nor a random trapcode makes a difference, it receives and shows all traps.

Is there some option I haven't seen? Or maybe is this some sort of bug?

Article Comments

Attention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.

Hello,

thank you very much for your KB-Post. I'm very much afraid alerting on received traps is currently only possible in a limited fashion in PRTG:How can I use PRTG’s trap receiver and what are its limitations?

But please be aware, that we will introduce a much more powerful SNMP Trap & Syslog Receiving engine very soon in PRTG:Sneak Peek into Our Labs: Introducing the New High Performance Syslog and SNMP Trap Receiver Sensors This will then make alerting on traps easily possible.

best regards.

Nov, 2013 - Permalink

Disclaimer:
The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.

Filtering of SNMP Trap Receiver doesn't seem to work

Article CommentsAttention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.

Search

Attention

Related Articles

Article Comments

Attention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.