On 15 December 2013 18:11, David Farrell <[email protected]> wrote: > >> On 15 Dec 2013, at 14:45, Gavin Henry <[email protected]> wrote: >> >> So we're monitoring everything possible inside our network but >> wondered what others do to check routes that come in to your network >> via transit for latency/pl etc.? With the mixture of transit and >> public peering, even on our startup network, it's something to think >> about the best way. Also, how far out do you monitor? Just to your BGP >> peers or some known point after that? It's not good just pinging some >> public service as I'm sure they won't like it. I hear Pingdom and >> others but not sure. > > Pingdom in use here. We monitor some key nodes that run BGP with it, and some > other bits and pieces within our hosted services. We're thinking about using > some VPS boxes around the globe to perhaps obtain different insights into how > we appear to the rest of the world. > > David.
Ok, thanks. I've got BGPMon and set up a NLNOG Ring too. Internal to outside monitoring is fine with Nagios (although looking at Opsview right now and Observium) and SmokePing. Mainly all SNMP with traps and Linux servers with NRPE. We have one external VM that we are adding to as it routes over LINX just now to us but want to check routes in via our two transit providers. -- Kind Regards, Gavin Henry.
