[147498] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: recommendations for external montioring services?

daemon@ATHENA.MIT.EDU (Edward Dore)
Mon Dec 12 14:19:32 2011

From: Edward Dore <edward.dore@freethought-internet.co.uk>
Date: Mon, 12 Dec 2011 19:18:07 +0000
In-Reply-To: <D2D37F15EBBD524693E9F3CB32D02080430C799D0E@exchange.corp.fpu-tn.com>
To: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

Take a look at Panopta - we use it to compliment our internal monitoring =
and find it great compared to some of the systems we've used in the past =
(Pingdom, Binary Canary).

The interface is easy to use and responsive, we don't get false =
positives and there are a good range of checks. There's an API as well =
if you want to integrate it.

I'd stay clear of the software agent though, we've had a few issues with =
that. For remote service checks we love it.

Edward Dore=20
Freethought Internet=20

On 12 Dec 2011, at 19:10, Eric J Esslinger wrote:

> I'm not looking to monitor a massive infrastructure: 3 web sites, 2 =
mail servers (pop,imap,submission port, https webmail), 4 dns servers =
(including lookups to ensure they're not listening but not talking), and =
one inbound mx. A few network points to ping to ensure connectivity =
throughout my system. Scheduled notification windows (for example, =
during work hours I don't want my phone pinged unless it's everything =
going offline. Off hours I do. Secondary notifications if problem =
persists to other users, or in the event of many triggers. That sort of =
thing). Sensitivity settings (If web server 1 shows down for 5 min, =
that's not a big deal. Another one if it doesn't respond to repeated =
queries within 1 minute is a big deal) A Weekly summary of issues would =
be nice. (especially the 'well it was down for a short bit but we didn't =
notify as per settings')
> I don't have a lot of money to throw at this. I DO have detailed =
internal monitoring of our systems  but sometimes that is not entirely =
useful, due to the fact that there are a few 'single points of failure' =
within our network/notification system, not to mention if the monitor =
itself goes offline it's not exactly going to be able to tell me about =
it. (and that happened once, right before the mail server decided to =
stop receiving mail).
>=20
> __________________________
> Eric Esslinger
> Information Services Manager - Fayetteville Public Utilities
> http://www.fpu-tn.com/
> (931)433-1522 ext 165
>=20
> This message may contain confidential and/or proprietary information =
and is intended for the person/entity to whom it was originally =
addressed. Any use by others is strictly prohibited.
>=20


home help back first fref pref prev next nref lref last post