From: Jason Boxman <jasonb@edseek.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Qdisc statistics project
Date: Wed, 13 Oct 2004 22:12:03 +0000 [thread overview]
Message-ID: <200410131812.03043.jasonb@edseek.com> (raw)
In-Reply-To: <200410121632.38611.alg0@iit.demokritos.gr>
On Tuesday 12 October 2004 09:32, Antonios Chalkiopoulos wrote:
> As a necessety for my job is to real-time monitor the bytes, packets,
> packet dropped etc of all the qdiscs working inside the kernel i've tried
> varius methods:
>
> 1. Parse tc -s command output and update a round robin database and use
> rrdtool to graphically display tc statistics.
I find that generally works.
> [varius perl scripts exist for the above job]
>
> 2. Unsuccesfully tried QoS SNMP extensions, in order to use a new MIB to
> extract qdisc stats from.
I was playing with that as well, but of late it doesn't seem to be actively
developed. Someone else mentioned LQL[1], but it doesn't seem to have hooks
to let you grab qdisc stats yet.
[1] http://www.coverfire.com/lql/
> There is also some work in the kernel level that will help reveal qdisc
> stats to userspace (thanks Thomas Graf)
Are you talking about tcstat[2]?
[2] http://reeler.org/tcstat/index.html
> To get to the point.. the perl parsing method is hackish and quick&dirty.
> A proper open-source tc monitoring tool SHOULD exist ! Maybe inside
> iproute2 maybe in sourceforge.
LQL seems to be the only actively developed project currently that could
eventually allow you to plug into netlink and poll for statistics. Right now
it seems you can only get and set parameters.
> Are there any volunteers to start working on such a project? I could put
> 4-6 weeks full time work on that... any suggestion for the most proper
> solution to the above problem is welcome.
I wrote yet another script to poll `tc` for statistics and pass that
information off to RRDTool via Perl's RRDs module. I am using it for
diagnostic purposes. It polls every 10s and updates a graph[3].
For long term tracking I am going to write a simple plugin for Munin[4] to
grab information every five minutes and pass that off for graphing.
[3] http://edseek.com/foo.png
[4] http://www.linpro.no/projects/munin/
--
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/
next prev parent reply other threads:[~2004-10-13 22:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-12 13:32 [LARTC] Qdisc statistics project Antonios Chalkiopoulos
2004-10-13 21:55 ` Jose Luis Araujo
2004-10-13 22:12 ` Jason Boxman [this message]
2004-10-14 5:18 ` Dan Siemon
2004-10-14 8:39 ` Antonios Chalkiopoulos
2004-10-14 18:22 ` Stef Coene
2004-10-14 18:55 ` Thomas Graf
2004-10-14 20:17 ` Stephen Hemminger
2004-10-14 20:27 ` Thomas Graf
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=200410131812.03043.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.