We wanted to monitor the reachability and responsiveness of our clients' websites. Obviously, you want to do this from multiple points and networks throughout the Internet. So what did we do?
We arranged for shell accounts with Perl, DBI for mySQL, and cron access. Then, every 15 minutes, the cron job measures ping times, packet loss, and the route. This data is then stored in a database on one of our servers locally. We also receive emailed alerts for high packet loss or total outage.
With that data and GD::Graph, we make some nice pretty graphs for our clients to see things like how hosting their website over that internal 64k ISDN line is a Bad Idea.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
RE: Distributed network monitor
by perlcgi (Hermit) on May 05, 2000 at 16:16 UTC | |
by Anonymous Monk on May 05, 2000 at 23:24 UTC | |
by perlcgi (Hermit) on May 06, 2000 at 21:50 UTC | |
by Novician (Novice) on May 08, 2000 at 13:54 UTC | |
by ChuckularOne (Prior) on May 08, 2000 at 21:29 UTC | |
by perlcgi (Hermit) on May 09, 2000 at 16:42 UTC | |
|
RE: Distributed network monitor
by Anonymous Monk on May 04, 2000 at 02:20 UTC | |
by comatose (Monk) on May 10, 2000 at 08:23 UTC |