New Question
 
 
PRTG Network Monitor

Intuitive to Use.
Easy to manage.

200.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free PRTG
Download >>

 

What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

 

Top Tags


View all Tags


Why does the SNMP Trap Receiver Beta have a polling period?

Votes:

0

Your Vote:

Up

Down

We are currently are trying to use the SNMP Trap receiver Beta to get real time updates from applications when problems arise. Upon testing this we noticed that PRTG doesn't do anything with the received trap until the polling period has been reached.

Why does the Trap receiver have a polling period, a trap should be instantaneous otherwise it's no better than an active polling sensor? Once the trap receiver receives the message it should immediately be acted upon.

Can you explain this behavior or have we misconfiguration something somewhere?

Thanks.

Michael

prtg snmp syslog trap trap-receiver

Created on Oct 8, 2014 10:47:58 AM by  michaeljdresser (0) 1

Last change on Jul 28, 2015 8:20:19 AM by  Luciano Lingnau [Paessler Support]



3 Replies

Votes:

0

Your Vote:

Up

Down

Dear Michael,

Please consider that the Trap Receiver Sensor is still in BETA state. Every sensor in PRTG has got a scanning interval due to the internal functioning. You can adjust the scanning interval to your needs in the settings of the sensor. Nevertheless I'll forward your request to our wish list for future versions of PRTG.

Best regards

Created on Oct 9, 2014 2:48:37 PM by  Felix Saure [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hello,
Speaking about pooling and trap receiving, can you please explain how does it work exactly? Is it possible to "miss" a trap because the pooling interval of the sensor is too big ? Is very any risk to lose traps?

As far as we understand the matter, we have to find a compromise:

  • large pooling interval -> we will know that something happens too late or we can lose the trap
  • small pooling interval -> the alarm is so quick that we do not notice it.

We need the alarm to be up for at least 30 seconds for every trap received and to be sure to receive 100% traps sent.

Thank you for your answer. Best regards

Created on Jul 24, 2015 2:22:49 PM by  ado_byes (0) 1

Last change on Jul 27, 2015 12:08:48 PM by  Luciano Lingnau [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hello ado_byes, your findings are correct.
With the current version of the Syslog and Trap Receivers, you can/must configure a scanning interval, because all sensors within PRTG require a scanning interval.

All messages will be received instantaneously, and be displayed within the sensor (in the messages tab and on the sensor's overview), the scanning interval currently affects the behavior of the Warning Filter and the Error Filter.
Once the scanning interval is over the received messages will be checked for messages matching the warning/error filters, the sensor's state will change and notifications will be processed. The Warning or Error states will be kept until the next scanning interval.

This link describes the sensor's working and behavior:
Blog: Introducing the New High Performance Syslog and SNMP Trap Receiver Sensors

Regarding the possibility of missing traps/syslog messages, that could only happen if the sensor is overloaded with a huge amount of messages at once, otherwise all messages will be received/store, regardless of interval.

Created on Jul 27, 2015 12:17:04 PM by  Luciano Lingnau [Paessler Support]



Please log in or register to enter your reply.


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.