[mrtg] Re: What stats are people monitoring?

[Koelstra, J. (Jan)]

Jeff,

Basically we use MRTG for trend analyzing for a wide range of items.
Monitoring and error-reporting is done with HP Openview/NNM.
In our organization we monitor the following with MRTG:
Routers
- traffic (do the lines have enough bandwith?)
- cpu load (is the router getting overloaded?)
- memory free (isn't any memory leaking?)
- roundtrip time to remote sites with mrtg-ping-probe (Is the delay
still acceptable?)
- number of active dial-in lines (When do we have to order an extra
PRI-line?)
Switches
- traffic on the uplink interface(s) (Is the bandwith sufficient?)
LAN's/VLAN's
- broadcast level (do we have to split the segment?)
Servers
- NIC traffic (just the same)
- cpu load (helps when sizing new machines)
- free diskspace (just the same)
- diskqueue length (just the same)
- memory pagefaults (just the same)
- memory allocated and free (just the same, but also to visualize
memoryleaks)
- # http hits (nice for the presentation to the management ;-) )
- # network connections (nice for the managers too, but also helpfull
for determining the number of required licenses for specific
applications)
- # mail messages sent/received to/from the oustide (mostly used for
detecting mail loops, also nice for the managers)
- temperature (Is the cooling system capable of keeping things under
control)
Printers
- number of printed pages (all users want to have their own printer, but
do they need one?)

I'm sure I missed a few small ones, but I think this is the main picture


Jan.


-----Original Message-----
From: Jeff Bolden [mailto:Jeff.Bolden at sterlingsavings.com] 
Sent: Wednesday, July 17, 2002 10:28 PM
To: mrtg at list.ee.ethz.ch
Subject: [mrtg] What stats are people monitoring?



Well, I am pulling stats down from 100+ routers and have more info than
I could possibly imagine... =) But it got me thinking about what info is
"critical" and what is just "nice to have" stuff. MRTG makes it easy to
get data-overload. Soo....

I was curious as to exactly what stats people are pulling from routers
for monitoring. I'm pulling some of the more obvious ones like Traffic,
Errors, Discards, FECNs/BECNs, Utilization, CPU and Data Buffers used
for my Frame links, and Traffic, Collisions, and Errors on my Ethernet
side. What else are people pulling to get the "big picture" of the
health of the WAN at your location, and why? =)

I feel like I'm missing something, but I've been staring at CFG's and
OID's for too long and can't think of anything... =)

Jeff Bolden

--
Unsubscribe mailto:mrtg-request at list.ee.ethz.ch?subject=unsubscribe
Archive     http://www.ee.ethz.ch/~slist/mrtg
FAQ         http://faq.mrtg.org    Homepage     http://www.mrtg.org
WebAdmin    http://www.ee.ethz.ch/~slist/lsg2.cgi

--
Unsubscribe mailto:mrtg-request at list.ee.ethz.ch?subject=unsubscribe
Archive     http://www.ee.ethz.ch/~slist/mrtg
FAQ         http://faq.mrtg.org    Homepage     http://www.mrtg.org
WebAdmin    http://www.ee.ethz.ch/~slist/lsg2.cgi