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.
Add comment