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


Notifications on errors from SNTP Traps

Votes:

0

Your Vote:

Up

Down

Is it possible to send notifications on every trap with error? Not by velocity or other aggregated values.

prtg snmp snmp-sensor

Created on Nov 24, 2017 7:07:09 PM by  Andrey_Ah (0) 1



3 Replies

Votes:

0

Your Vote:

Up

Down

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.

Created on Nov 27, 2017 2:17:51 PM by  Torsten Lindner [Paessler Support]



Votes:

0

Your Vote:

Up

Down

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.

Created on Nov 27, 2017 4:29:22 PM by  Andrey_Ah (0) 1



Votes:

0

Your Vote:

Up

Down

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.

Created on Nov 28, 2017 10:05:04 AM by  Torsten Lindner [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.