KnightGuard.Net
User's Guide
Statistical Reports
Every week, you'll receive an e-mail report of the
previous week's activity. You'll see at a glance how many times
your site was monitored, how many times your site was not responsive,
responded too slow, and the minimum, maximum and average page retrieval
times for each day of the week.
Here's an example of the standard HTML based e-mail
report:
Statistics for Week beginning Sat Aug 25
Monitoring Statistics for http://www.knightguard.net/
| |
|
|
|
|
|
Retrieval Times (seconds) |
| Day |
Times
Monitored |
Failures |
Retrieved
Late |
Title/Page
Errors/Changes |
Min |
Avg |
Max |
| Sun |
96 |
1 |
0 |
0 |
0.270 |
0.311 |
0.652 |
| Mon |
96 |
0 |
0 |
0 |
0.267 |
0.343 |
0.861 |
| Tue |
95 |
0 |
0 |
0 |
0.270 |
0.410 |
5.599 |
| Wed |
96 |
2 |
0 |
0 |
0.270 |
0.330 |
0.729 |
| Thu |
96 |
0 |
1 |
0 |
0.274 |
0.347 |
1.580 |
| Fri |
96 |
0 |
0 |
2 |
0.270 |
0.332 |
1.120 |
| Sat |
96 |
0 |
0 |
0 |
0.268 |
0.300 |
0.437 |
|
These statistics show that on any given day, the URL in question
was monitored 96 times, except on Tuesday when the count is 95.
Perhaps network congestion prevented an accurate monitoring cycle,
and KnightGuard.Net aborted the cycle rather than report a false
alarm.
On Wednesday, the monitored URL failed to respond twice.
On Thursday, the site took longer than the desired time (see Sensitivity)
to retrieve the page. Also in Thursday, the average page retrieval
time was 0.347 seconds. Page retrieval times exclude error conditions
like failures and late retrievals.