Got argus installed easily, now what?

[Kevin C Miller]

For what it's worth, we've recently been looking at creating a package to 
allow dynamic graph generation, etc. This is just in its infancy though.

I will note that while an SQL backend sounds like it'd be very sexy, in 
practice I'm not sure how fast/well that'll scale. Right now we're logging 
(to disk) about 38 million records/hour; I don't believe we'd be anywhere 
near capable of replacing our disk logs with a DBMS and
a) still be able to store all the records
b) be able to run queries on historical data nearly as quickly

So while it might be interesting to have the SQL backend, our design of a 
general purpose filter-and-graphing daemon will most likely expect either a 
live stream or a flowfile.

For actually generating the graphs, we're probably thinking RRD databases, 
given the existing tools to generate graphs and the RRD database 
performance as it relates to the same.

-Kevin

--On Saturday, November 23, 2002 12:54 AM +0300 Mitesh P Choksi 
<mitesh at icafe.co.tz> wrote:

> Primary reason for installing argus: IP based bandwidth accounting
> Secondary: Protocol usage analysis
> ...: Answering question what happened in "that" peak hour, who used for
> what?
>
> A SQL backend to store all argus information realtime would be fantastic.
> I would plug all the info into MySQL and then use graphical reporting
> tools to get reports out for history or current information.



---------------------------------------------------
Kevin C. Miller <kcm at cmu.edu>
Network Group
Carnegie Mellon University