[EMAIL PROTECTED] wrote on 01/10/2007 06:30:36 PM:
> I see, perhaps this is why Flowviewer is taking too long when
> showing flow reports for a long span of time. I wonder if Flowviewer
> guys have already considered this.
Yes, FlowViewer adds very little processing time to it's basic role,
invoking:
flow-cat | flow-nfilter | flow-stat
Example:
/usr/bin/flow-cat -t "01/10/2007 02:44:59" -T "01/10/2007 04:30:01"
/htp/flows/router_1/2007/2007-01/2007-01-10 | /usr/bin/flow-nfilter -f
/htp/cgi-bin/Flow_Working/FlowViewer_filter_052901 -FFlow_Filter |
/usr/bin/flow-stat -f11 -S3
>/htp/cgi-bin/Flow_Working/FlowViewer_output_052901
Then FlowViewer simply prints the resulting output file to the browser.
The only additional processing is resolving DNS names if requested, but it
puts these in a cache to speed things up on subsequent runs.
Same with FlowGrapher, except it keeps track of flows by size in order to
come up with the largest 'detail lines' lines of textual output. Thus, the
lower the 'detail lines' value the faster the response time.
FlowTracker is only looking at a five-minute window, so it is pretty
quick.
You may want to write a script that runs once a day, generates the current
day's stats, and accumulates those into a running total of traffic by
country.
Joe
_______________________________________________
Flow-tools mailing list
[EMAIL PROTECTED]
http://mailman.splintered.net/mailman/listinfo/flow-tools
