We can then choose the sound file we'd like to play and test the alert. If we'd like our sound to play when alert conditions start, we'll select When alert conditions start. Once we've set our conditions, we will set the event notification preferences of our alert. We can then enter the various values for our condition. For our example, we’ll select Latency or Packet Loss Over Time from the dropdown menu. ![]() We will then be prompted to enter our alert conditions. ![]() In our case, we will select Play a Sound from the Create a New Alert menu. Every alert will be stored in our alert library for use on any target.įor example, we'll be setting up an alert that will play a buzzer sound any time our target experiences latency higher than 250 milliseconds for 10% (or more) of a 10-minute timeframe.įirst, we'll select an alert type. To set up a new alert, either select a target from a summary screen or open a trace window for a target, then click on the Alerts tab.įrom here, we're able to create a new alert. If you're trying to show your ISP there's a problem, you might log your PingPlotter data to a file so you have a record of every time conditions deteriorate. WAV file (if you're usually within hearing distance) or both. You can attach an alert within PingPlotter to that IP address so that you receive an email alert if the last 10 of 10 sample requests are lost.Īnother possible alert condition could be set when latency exceeds a specific threshold. Alerts are automated events that trigger when specific network conditions occur.įor example, let's say you need to know when a destination you're monitoring stops responding.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |