[collectd] Collecting more detail network statistics

Bruno Prémont bonbons at linux-vserver.org
Sat Feb 28 11:25:43 CET 2009


Hi Ulf,

Using the "netlink" plugin to collect interface statistics you get the
error counters for your interface (assuming you put the interface in
VerboseInterface)
The older "interface" plugin provides only a limited subset of
statistics for your interface (those netlink plugin provides for those
interface that are in it's "Interface" config option but not in
"VerboseInterface")

Unfortunately it's not very clear what values you are interested in...
If you want some specific stats exported by SNMP on your server you
could also collect them with snmp plugin.

Regards,
Bruno 

On Fri, 27 February 2009 "Ulf Zimmermann" <ulf at openlane.com> wrote:
> I am looking at how I could collect more detailed network (interface)
> statistics. Extra numbers I am interested in are (all on Linux
> database servers):
> 
> > netstat -in
> Kernel Interface table
> Iface       MTU Met    RX-OK RX-ERR RX-DRP RX-OVR    TX-OK TX-ERR
> TX-DRP TX-OVR Flg
> bond0      9000   0 4427744155      0    344      0 4494207846      0
> 0      0 BMmRU
> bond1      1500   0 17107572826      0 14154233      0 32041369000
> 0      0      0 BMmRU
> bond1:4    1500   0      - no statistics available -
> BMmRU
> eth0       1500   0 17094933377      0 14154233      0 32041368995
> 0      0      0 BMsRU
> eth1       9000   0 4427744129      0    344      0 4494207840      0
> 0      0 BMsRU
> eth2       1500   0 12639449      0      0      0        5
> 0      0 0 BMsRU
> eth3       9000   0       26      0      0      0        6
> 0      0 0 BMsRU
> lo        16436   0 153870174      0      0      0 153870174      0
> 0      0 LRU
> > cat /proc/net/snmp
> Ip: Forwarding DefaultTTL InReceives InHdrErrors InAddrErrors
> ForwDatagrams InUnknownProtos InDiscards InDelivers OutRequests
> OutDiscards OutNoRoutes ReasmTimeout ReasmReqds ReasmOKs ReasmFails
> FragOKs FragFails FragCreates
> Ip: 2 64 21654572736 0 7380 0 2 0 21651696350 36685339936 96045 0 2
> 5738006 2869002 2 2869003 0 0
> Icmp: InMsgs InErrors InDestUnreachs InTimeExcds InParmProbs
> InSrcQuenchs InRedirects InEchos InEchoReps InTimestamps
> InTimestampReps InAddrMasks InAddrMaskReps OutMsgs OutErrors
> OutDestUnreachs OutTimeExcds OutParmProbs OutSrcQuenchs OutRedirects
> OutEchos OutEchoReps OutTimestamps OutTimestampReps OutAddrMasks
> OutAddrMaskReps Icmp: 179399 539 72287 75 0 0 6175 87346 13516 0 0 0
> 0 160712 0 73365 1 0 0 0 0 87346 0 0 0 0
> Tcp: RtoAlgorithm RtoMin RtoMax MaxConn ActiveOpens PassiveOpens
> AttemptFails EstabResets CurrEstab InSegs OutSegs RetransSegs InErrs
> OutRsts
> Tcp: 1 200 120000 -1 1517920 13022694 631 736932 154 17526834826
> 32440334577 1799855 90 1726588
> Udp: InDatagrams NoPorts InErrors OutDatagrams
> Udp: 4118310725 71447 1421 4244831166
> 
> As you can see there is a bunch of dropped RX packets on the
> interfaces (we are looking into problems and trying to correlate
> those dropped packets with problems we are encounter). Other numbers
> like reassemble and other errors are of general interest too.
> 
> Is anyone collecting these numbers right now? Any hints how you would
> collect them?
> 
> Regards, Ulf.



More information about the collectd mailing list