From: Les Mikesell <les@futuresource.com>
To: Daniel Chemko <dchemko@smgtec.com>
Cc: netfilter@lists.netfilter.org
Subject: RE: bandwidth monitoring
Date: Thu, 06 Jan 2005 13:39:48 -0600 [thread overview]
Message-ID: <1105040388.14796.64.camel@moola.futuresource.com> (raw)
In-Reply-To: <7C9884991ADAE0479C14F10C858BCDF591E3AA@alderaan.smgtec.com>
On Thu, 2005-01-06 at 13:04, Daniel Chemko wrote:
> I'll address this as well. Ntop is fantastic at giving you snapshot data
> of a network, but it is inanely heavy at long term monitoring of
> services. It got to the point that monitoring traffic from the firewall
> filled memory and CPU usage if run long enough. It doesn't work for
> continuous operations.
The thing to keep in mind is that it is keeping a database that
includes all of the remote IP addresses and ports as well as the
local ones, so of course this will grow quickly. I haven't needed
to deal with long-term histories so I haven't investigated the
possibilities but I do recall something about ntop being able
to start new logs and archive the old ones as needed to limit
the active size. There are tools to monitor and summarize
netflows between each pair of addresses, but again I haven't
used that part of the package. There is also some support for
RRD databases which would probably be the way to go for longer
histories.
--
Les Mikesell
les@futuresource.com
next prev parent reply other threads:[~2005-01-06 19:39 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-06 19:04 bandwidth monitoring Daniel Chemko
2005-01-06 19:39 ` Les Mikesell [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-10-29 0:44 Bandwidth monitoring David H. Lynch Jr.
2012-10-29 11:46 ` Christian Lamparter
2012-10-28 15:37 David H. Lynch Jr.
2012-10-28 20:59 ` Christian Lamparter
2012-10-23 18:58 David H. Lynch Jr.
2012-10-24 6:35 ` Christian Lamparter
2012-10-21 19:58 David H. Lynch Jr.
2012-10-22 10:43 ` Christian Lamparter
2005-01-07 5:48 bandwidth monitoring Patrich Björklund
2005-01-06 20:28 Daniel Chemko
2005-01-06 16:28 patrick.leduc
2005-01-06 17:09 ` J. Nerius
2005-01-06 17:42 ` Les Mikesell
2005-01-06 17:56 ` J. Nerius
2005-01-06 20:09 ` Michael Gale
2005-01-06 20:19 ` J. Nerius
2005-01-06 21:28 ` Michael Gale
2005-01-06 21:54 ` J. Nerius
2005-01-06 23:30 ` Michael Gale
[not found] ` <41DDA135.5000205@cisco.com>
2005-01-06 21:24 ` Michael Gale
2005-01-07 1:54 ` Mark E. Donaldson
2005-01-10 13:45 ` Fabiano Reis
2005-01-26 18:33 ` Ranjeet Shetye
2005-01-26 20:00 ` Jose Maria Lopez
[not found] <04a901c36e18$ad2d6650$2a0110ac@SAMHP>
2003-08-31 1:03 ` Bandwidth Monitoring Arnt Karlsen
2003-09-01 7:33 ` Ray Leach
2003-09-04 6:34 ` Dharmendra.T
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=1105040388.14796.64.camel@moola.futuresource.com \
--to=les@futuresource.com \
--cc=dchemko@smgtec.com \
--cc=netfilter@lists.netfilter.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.