[151496] in North American Network Operators' Group
RE: Monitoring other people's sites (Was: Website for ipv6.level3.com
daemon@ATHENA.MIT.EDU (Frank Bulk)
Fri Mar 23 00:28:07 2012
From: "Frank Bulk" <frnkblk@iname.com>
To: "'Jeroen Massar'" <jeroen@unfix.org>
In-Reply-To: <4F689A15.8020707@unfix.org>
Date: Thu, 22 Mar 2012 23:27:09 -0500
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
I and my customers users IPv6-enabled sites. If it doesn't work (a =
hopefully their web browser uses HE) I want to know, and know when it =
happens. Yes, many sites aren't monitoring their own IPv6-connected =
content, but I've had reasonably good success privately letting them =
know when it's down. And communicating to them when it's down lets them =
know that people care and want to access their IPv6-enabled content. =
Last, monitoring IPv6 access to many different sites brings our own =
connectivity issues to the surface as they arise -- we had one inside =
Level3's network last week Friday and it was resolved about 18 hours =
later. If we had not monitored it's possible it would be much longer =
before it was discovered and troubleshot through the regular sequence of =
events.
Frank
-----Original Message-----
From: Jeroen Massar [mailto:jeroen@unfix.org]=20
Sent: Tuesday, March 20, 2012 9:54 AM
To: Vinny_Abello@Dell.com
Cc: nanog@nanog.org
Subject: Monitoring other people's sites (Was: Website for =
ipv6.level3.com returns "HTTP/1.1 500 Internal Server Error")
<snip>
And for the few folks putting nagios's on other people's sites, they
obviously do not understand that even if the alarm goes off that
something is broken that they cannot fix it anyway, thus why bother...
