All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Boxman <jasonb@edseek.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Traffic Control Diagnostic Graphing Utility
Date: Wed, 27 Oct 2004 04:23:03 +0000	[thread overview]
Message-ID: <200410270023.03178.jasonb@edseek.com> (raw)

I wrote a Perl script to poll `tc` for traffic control statistics (just bytes 
presently) for leaf qdiscs.  The information is fed to either RRDTool or 
Munin[2], depending on what parameter is passed to the script.  If the option 
for a RRD database is used, graphs[3][4] are written to disk for each ten 
second polling interval.  If invoked via Munin[2], it handles graphing and 
samples at five minute intervals.

[1] http://ee-staff.ethz.ch/~oetiker/webtools/rrdtool/
[2] http://www.linpro.no/projects/munin/
[3] http://trekweb.com/~jasonb/images/eth0-24-tc.png
[4] http://trekweb.com/~jasonb/images/eth0-1-tc.png

The aim is to graphically represent bandwidth utilization for each leaf class 
to help diagnose issues with misclassification, performance, and for long 
term profiling.

The script is available[5] here.  The included README explains basic 
configuration.

[5] http://trekweb.com/~jasonb/code/polltc-1.0.tar.gz

I hope someone else finds it useful.

Comments welcome.

-- 

Jason Boxman
Perl Programmer / *NIX Systems Administrator
Shimberg Center for Affordable Housing | University of Florida
http://edseek.com/ - Linux and FOSS stuff

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

             reply	other threads:[~2004-10-27  4:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-27  4:23 Jason Boxman [this message]
2004-10-27 11:17 ` [LARTC] Traffic Control Diagnostic Graphing Utility vicente
2004-10-27 14:46 ` magin
2004-10-27 18:33 ` magin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200410270023.03178.jasonb@edseek.com \
    --to=jasonb@edseek.com \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.