From: "Jay Wineinger" <shad@wnoc.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] API using cbq / tc ?
Date: Mon, 10 Feb 2003 18:01:03 +0000 [thread overview]
Message-ID: <marc-lartc-104490024712807@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104453716713244@msgid-missing>
That isnt completely accurate. rrdtool can take data at any interval, you
just need to specify it when you create the rrd file. Personally, I get
snmp data on 2 interfaces every 10 seconds and store them in two rrd files,
and I have a php page that generates new graphs every time I view them (I
migrated away from mrtg completely and just use rrd to store and graph).
This was, the only consistent load on the box is from the snmp gathering
(which is a local connection). The graph script runs only once every time
the page is viewed, so the load is quite low there. however, I do agree that
doing it all on the client would be better, but for a distributed viewing, a
webpage makes a nice interface.
jay
----- Original Message -----
From: "Stef Coene" <stef.coene@docum.org>
To: <mingching.tiew@redtone.com>; <lartc@mailman.ds9a.nl>
Sent: Monday, February 10, 2003 3:59 AM
Subject: Re: [LARTC] API using cbq / tc ?
> On Monday 10 February 2003 02:58, mingching.tiew@redtone.com wrote:
> > Cool. As an MRTG idiot, I am going to ask this question,
> > why can't it provide realtime stats ? You mean MRTG
> > does not chart real time graphs ?
> Mrtg is not designed for that. Mrtg uses rrdtool to generate the graphs.
> You give the rrdtool each 5 minutes a number. This number is stored in a
rrd
> file. And you can generate a graph with the data in the rrd file.
>
> So it's for long-term graphing. If you want to do real time graphing, you
> need new data each second. And you need to generate the graph on the
client
> side so you don't need to load each second a new graph from the server.
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-02-10 18:01 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-06 13:20 [LARTC] API using cbq / tc ? Srikanth
2003-02-07 2:28 ` S Mohan
2003-02-07 4:37 ` Srikanth
2003-02-07 7:44 ` Stef Coene
2003-02-08 7:02 ` Ming-Ching Tiew
2003-02-08 10:39 ` Stef Coene
2003-02-08 13:04 ` Ming-Ching Tiew
2003-02-08 13:22 ` Stef Coene
2003-02-09 3:45 ` Ming-Ching Tiew
2003-02-09 7:26 ` Henry Yen
2003-02-09 13:39 ` Stef Coene
2003-02-10 1:58 ` mingching.tiew
2003-02-10 8:59 ` Stef Coene
2003-02-10 18:01 ` Jay Wineinger [this message]
2003-02-10 18:20 ` Stef Coene
2003-02-11 16:59 ` Martin Devera
2003-02-11 18:16 ` Stef Coene
2003-02-12 8:29 ` devik
2003-02-12 17:45 ` Stef Coene
2003-02-13 8:30 ` devik
2003-02-13 10:36 ` mingching.tiew
2003-02-13 18:39 ` Stef Coene
2003-02-13 18:40 ` Stef Coene
2003-02-14 3:58 ` mingching.tiew
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-104490024712807@msgid-missing \
--to=shad@wnoc.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.