 |
|
 |
|
Getting notified of a network problem PingPlotter can be set up to continuously monitor your network, and to notify you when it finds a problem. This notification capability in PingPlotter is called Alerts. Along with being powerful, alerts can also be slightly complicated. Because of this, we'll start out talking about alerts, and then go through some hands-on exercises to actually configure some alerts with you. So what is an Alert? Alerts monitor conditions of a specific IP Address, and then do something when those conditions are met or exceed a specified range. Some examples of what you can alert on are:
PingPlotter gives you five different alert events, or what it will do if a condition is met:
The great thing about PingPlotter's alert system is that you can combine any of the five types of events, all within the same alert tied to an IP Address, and each with their own trigger mechanisms. Those triggers mechanisms are:
We cover these triggers in detail in the PingPlotter Tutorial and Product Manual. Let's start with covering the theory behind the alert system, and then move right into the hands-on exercises. The alert system in PingPlotter is based on a Many to Many type of relationship between routers/targets and alerts. What this means is that you can setup one alert, and then use that alert on many different targets and/or hops. Conversely, you can have one hop that has many alerts tied to it. Taking that a step further, as mentioned above, each one of those alerts can have any or all of the five alert events configured within it. In the first hands-on exercise, we'll setup a simple Tray Icon Alert to get familiar with the alert interface. If you're new to alerts, this is the alert we recommend you start with. Once we have the basics of alert configuration down, we'll build on that and do a Send an Email alert. Our Product Manual and Tutorial has a section that covers alerts in depth, and a specific section on troubleshooting alerts. You are encouraged to go there for further reading.
|
