From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] /proc interface OR graphing again ?
Date: Mon, 09 Sep 2002 17:13:41 +0000 [thread overview]
Message-ID: <marc-lartc-103159168605619@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103156942814205@msgid-missing>
On Monday 09 September 2002 19:59, raptor wrote:
> hi,
>
> I was searching in the arhives(for tcng-htb patch, still searching !!) and
> found a discussion about /proc interface for the ip-statistics/qos ..... is
> there any advance on this ?
Not that I know ....
> Current practice is to install ipchains/iptables for counting the traffic
> and then graph the results with ip"something!" (computionaly intensive)....
> i probably will take the approach a separate station in promicious mode..
> but availability of the counters in the /proc can streamline the things
> alot and give a quick way with simple scripts to handle those things...
> And the idea to polling this statistics later with mrtg via net-snmp is
> good :")
I have some scripts that uses the rrdtool (that's the graping part of mrtg) to
create graphs based on the counters in tc. It also uses snmp to get the
information so you can monitor on an other box. The scripts are ugly and I
have some snmp-related problems, but it works for me. (see docum.org on the
gui page for an exampe).
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.oftc.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-09-09 17:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-09 11:03 [LARTC] /proc interface OR graphing again ? raptor
2002-09-09 17:13 ` Stef Coene [this message]
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=marc-lartc-103159168605619@msgid-missing \
--to=stef.coene@docum.org \
--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.