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


Setting sensor to not auto-clean

Votes:

0

Your Vote:

Up

Down

Hello,

every alarm when the sensor identifies that the threshold has been resolved is cleared.

We have some cases that for ping sensors, where the data link has much oscillation, generate many alarms and this causes operational problems for the NOC.

We know we can make some settings to make the sensor less sensitive, but we want to do a different configuration.

We want the ping alarms for these data links to be cleared by an operational team when they are sure that the data link has stabilized.

Is it possible to do this?

Is it possible to do this configuration of type template and apply on all devices that we want, without having to configure individually?

Thank you.

alarm prtg sensor snmp wmi

Created on Sep 24, 2018 2:06:37 AM by  Sandro Alves (6) 1



3 Replies

Votes:

0

Your Vote:

Up

Down

Hello Sandro,

I'm afraid there is no "out of the box" option like "Keep down state until further notice" or something like that. What you could do would be using a notification that pauses the sensor with an API call. That way it will be paused until being resumed manually again. See "Setup | PRTG API | Object Manipulation" where the API call for pausing is explained.

Kind regards,

Erhard

Created on Sep 24, 2018 11:37:20 AM by  Erhard Mikulik [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hello,

thanks for the answer, but this solution will generate some operational problems.

Once the sensor has been paused, we will lose data link information collection.

What we thought of doing is to use a trigger to start the device again after a few minutes if it was normalized. But that will not help.

Currently how alarm management for data linking works in another monitoring solution we use:

Action 1: Sensor detects a problem; Action 2: Created an alarm (Critical) for this problem; Action 3: Opening of external ticket; Action 4: As long as the problem exists, the alarm created for this incremental problem counts every x check-time period; Action 5: Sensor detects normality; Action 6: Alarm changes to (information) of this problem; Action 7: After 30 minutes a script changes the alarm message, informing the NOC to close ticket; Action 8: The ticket system automatically closes the alarm.

This process ensures that in case of very frequent data link oscillation, the NOC is responsible for ensuring that the data link has actually returned and is not oscillating.

This ensures a quality in sending the communications to our customers accurately.

Our goal is to only handle alarms without affecting the information being collected. Therefore, alarm management in the PRTG would be very important for us working with MSP and managing many bad data links in Brazil.

You said that there is no factory setting, so reinforce the question. Is there any option that is even development to meet this need?

Thank you.

Created on Sep 25, 2018 3:27:16 PM by  Sandro Alves (6) 1



Votes:

0

Your Vote:

Up

Down

Hello Sandro,

Please find here how to address feature requests, so we can see how many other users might be interested in this as well.

Kind regards,

Erhard

Created on Sep 26, 2018 8:35:00 AM by  Erhard Mikulik [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.