From: Jose Luis Araujo <jlaraujo@mercs.homeip.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Qdisc statistics project
Date: Wed, 13 Oct 2004 21:55:23 +0000 [thread overview]
Message-ID: <416DA44B.5060001@mercs.homeip.net> (raw)
In-Reply-To: <200410121632.38611.alg0@iit.demokritos.gr>
Hi Antonios.
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 have developed myself a similar setup, but i used a perl script with
snmp pass_persist to retrieve the data via snmp feed it to MRTG and then
display it with a CGI script, since i changed jobs recently i made some
changes to the setup and was thinking in creating a sourceforge project.
But i don't think it is ready for that yet, i mean, it is working
beautifully for me (and in my previous employer) but there are some
rough edges to address first.
Btw, the setup generates TC, iptables and MRTG configuration from a
config file.
I think it is time to see how can the setup be improved.
>[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.
>
>There is also some work in the kernel level that will help reveal qdisc stats
>to userspace (thanks Thomas Graf)
>
>
I have never heard of this, must google it.
>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.
>
>
I really never tried to write a better tool, with less 'tc -s' parsing,
don't have the time or incentive to hack the needed code, so can't help
you there :-)
>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 can forward you the software that i use with some documentation.
>Thanks,
>Antonio
>_______________________________________________
>LARTC mailing list / LARTC@mailman.ds9a.nl
>http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>
>
Hope it Helps
José Araújo
_______________________________________________
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 21:55 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 [this message]
2004-10-13 22:12 ` Jason Boxman
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=416DA44B.5060001@mercs.homeip.net \
--to=jlaraujo@mercs.homeip.net \
--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.