[75072] in North American Network Operators' Group
Re: Network Monitoring System - Recommendations?
daemon@ATHENA.MIT.EDU (Alexei Roudnev)
Sat Oct 30 12:38:30 2004
From: "Alexei Roudnev" <alex@relcom.net>
To: "Andy Dills" <andy@xecu.net>,
"Charlie Khanna - NextWeb" <charlie@nextweb.net>,
"Rob Nelson" <ronelson@vt.edu>
Cc: <nanog@merit.edu>
Date: Sat, 30 Oct 2004 09:37:34 -0700
Errors-To: owner-nanog-outgoing@merit.edu
>
>
> >Nothing all in one place, that I'm aware of. But with a little work, you
snmpstat have hardcoded set of monitored parameters, but creates all graphs
anb links automartically, including customer-only view of customer's links,
link to the database record about this link, and link to the router's config
@ CCR.
This is why we use combination - for 99% of partameters, snmpstat, and for
the rest, hand-configured cricket (but I recommend nagios).
> >could probably integrate it all into nagios. After all, you can make the
> >host names or descriptions URLs that link to bandwidth and error graphs
or
> >other tools.
>
> I'll second this part. Whether you use cricket or MRTG, or even Nagios
> itself, you can use a little "notes_url" command to create a link from,
> say, the "ping" service of your core router to the MRTG charts of
bandwidth
> usage.
>
> Rob Nelson
>
> Rob Nelson
> ronelson@vt.edu
>
