SiteScope User's Guide
![]() |
![]() |
![]() |
![]() |
The SiteScope Ping Monitor checks the availability of a host via the network. Use this monitor to ensure that your connection to the Internet is alive and well.
Each time the Ping Monitor runs, it returns a reading and a status message and writes them in the monitoring log file. It also writes the total time it takes to receive a response from the designated host in the log file.
Why should I use this monitor?
The network can often be a web traffic bottleneck, especially on relatively slow wide area network connections. The Ping Monitor obtains two of the most common measurements used to determine if your network connection is congested: Round Trip Time and Loss Percentage. An increase of either of these suggests that you're experiencing problems. In the case of Loss Percentage, you want to see a 0% reading. A 100% reading indicates your link is completely down. Some loss may happen very occasionally, but if it becomes common, the network is either flaky (some packets are being lost), or very busy and the router may be dropping the Ping packets.
What should I be monitoring?
We suggest that you set up monitors that test your connection to the Internet at several different points. For example, if you have a T1 connection to a network provider who in turn has a connection to the backbone, you would want to set up a Ping Monitor to test each of those connections. The first monitor would ping the router on your side of the T1. The second would ping the router on your provider's side of the T1. The third monitor would ping your provider's connection to the backbone.
In addition to these monitors, it's also a good idea to have a couple of other monitors ping other major network providers. These monitors won't really tell you whether the other provider is having a problem, but it will tell you if your network provider is having trouble reaching them.
How often should I schedule Ping Monitors to run?
Because it won't cost you much performance wise, you can monitor your own router as often as every two minutes or so. That way you will know about any problems on your end as quickly as possible. The monitors that watch your provider's connection to your line and to the backbone should only be run every ten minutes or so. This will minimize traffic while still providing you with sufficient coverage.
To display the Ping Monitor Form, either click the Edit link for an existing Ping Monitor listed in a monitor table, or click the add a Monitor link on a group's detail page and choose the "New Ping Monitor" link.
Complete the items on the Ping Monitor form as follows. When the required items are complete, click the Add Monitor button.
The advanced options give you the ability to customize error and warning thresholds. If you choose not to set them, SiteScope will use pre-set defaults if available. If a default is not available, SiteScope will not be able to utilize the condition.
Note: In order to change the run frequency of this monitor when an error is detected, use the Update every (on errors) option below.
Note: The status returned by the Verify Error run of the monitor will replace the status of the originally scheduled run that detected an error. This may cause the loss of important performance data if the data from the verify run is different than the initial error status.
Warning: Use of this option across many monitor instances may result in significant monitoring delays in the case that multiple monitors are rescheduled to verify errors at the same time.
You can change this to generate an error based on the average length of the round trip times. To change the default choose either % packets good or round trip time from the drop-down menu. Next choose a comparison symbol from the list. Use the comparison value list to specify an error threshold.
Finally, enter the comparison value in the last text entry box to create a complete equation, such as % packets good <= 90.
SiteScope's reported round trip time is actually the average of the round trip times from all five pings executed each time the monitor runs. Enter the lowest average round trip time (in milliseconds) which should trigger an error status.
To set the warning threshold, choose either % packets good or round trip time from the drop-down menu. Use the comparison operator list to specify >= (greater than or equal to), != (not equal to), or < (less than). Finally, enter the comparison value in the last text entry box to create a complete equation, such as % packets good <= 99.
SiteScope's reported round trip time is actually the average of the round trip times from all five pings executed each time the monitor runs. Enter the lowest average round trip time (in milliseconds) which should trigger a warning status.
To set the Good if threshold, choose either % packets good or round trip time from the drop-down menu. Next choose a comparison symbol from the list. Use the comparison value list to specify an good threshold.
Finally, enter the comparison value in the last text entry box to create a complete equation, such as % packets good >= 90.
![]() |
![]() |
![]() |
![]() |

Copyright © 2003 Mercury Interactive Corporation.
All rights reserved.