[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Subject: ip accounting -> PostgreSQL

All what we need is: source IP, destination IP, source port, destination
port, bytes, time.
For now nacctd periodically stores this information in the text file, and
simple perl script (periodically) moves fresh data to MySQL.
But we like the idea to put it directly into database. Why Postgres? It
have some features that we want to use in the future.
Maybe we missing something important?


On Thu, 7 Feb 2002, Kevin Littlejohn wrote:

> There's a whole slew of ways you can do this, and it'll depend a lot on
> how much detail you need.  Probably the best approach is to settle on a
> front-end system of some sort - be it argus for full netflow-like reporting,
> or some sort of snmp poller if you're looking for snmp data, or whatever,
> then hack up an import system that can run periodically and import all
> data from a given directory into the database.  That saves you from having
> to worry about what happens if the database is down, too.
> On Wed, Feb 06, 2002 at 07:38:39PM +0500, Nicholay P. Chuprynin wrote:
> > 
> > Hello All.
> > We need to do IP based traffic accounting on our server, but the main
> > question is to store accounting information into PostgreSQL database.
> > Any suggestions?

Reply to: