If a Sensor or a complete Device, on a Virtual machine for example, has a loop of loose contact, a new connect and a loose contact over and over again - a message shower of Notifications up to 300 Mails per day are sent.

There is no way to limit this. Please fix this.

Article Comments

Hi there,

Which settings do you configure in your notification triggers and notification template. This email spam can be reduced by using the option "Notification Summarization > Method". This option allows you to summarize notification during a certain time and then send a notification.

Another way would be to increase the time option in your notification trigger. Instead of "When sensor state is Down for at least 60s" change the setting to "When sensor state is Down for at least 300s".
The last option would be to change the behavior of the Sensor. In the Sensor setting you can find the option "Scanning Interval > If a Sensor Query Fails....". Here you can define for how many intervals the Sensor should be in the "Warning" state before it goes into the "Down" state.


Jan, 2020 - Permalink

Yes, we have all checked this, it doesn't work, when a loop of loosing contact.

1) Send first DOWN message ASAP, then summarize: 1 minute is set.

2) When sensor state is Down for at least 280 seconds, perform E-Mail Group XXX When sensor state is Down for at least 300 seconds, perform no notification and repeat every 0 minutes When sensor leaves Down state after a notification was triggered, perform E-Mail Group XXX

Screenshots see Case PAE1293081


Jan, 2020 - Permalink

Hi,

notice you already have a case open. Therefore, my colleague will work further on this issue.

If you have any further questions, please do not hesitate to contact us again.


Jan, 2020 - Permalink

The Case is closed. I should post a feature request. There is no solution for intermittent contacts at Sensors.

(This is unfortunately not possible, the only way to solve this behavior with intermittent contacts is to eliminate the error that is displayed in the sensor.)


Jan, 2020 - Permalink

Hi,

my colleague is correct. The main issue is that the Sensor flips between up and down and this cause many emails. So to resolve this spam, we should focus at the error displayed in the Sensor.
However for this troubleshooting steps, I recommend to use the ticket since it's easier to share logs and screenshots via email.


Jan, 2020 - Permalink

There are no more troubleshooting steps.

We have other Systems like Veeam, these systems have two global Parameters: Count xx Max Errors per yy day

The Result is one last Message: The sensor xxxx has reached the maximum number of 10 errors per day. The notification is paused for next 8 hours.

This feature is the solution for this kind off errors.


Jan, 2020 - Permalink

Hi,

At the moment, we have noch such a feature. The only similar feature is to increase the period in which PRTG summarize notification.
However, if you want to forward a feature request, please follow the steps described here


Jan, 2020 - Permalink