I see, thanks for the input. The simplest solution i'd have for you is
to use post_tag (or post_tag2), if you are not using tags for anything
else. Essentially: you add 'tag' to your 'aggregate' line (and modify
your SQL schema to reflect that) and add to your config 'post_tag: X'
where X is a positive integer number different for each pmacct server.
Would that work for you?
On Tue, Aug 22, 2017 at 05:45:22PM +0200, fboehm wrote:
> Am 2017-08-22 um 16:45 schrieb Paolo Lucente:
> >Hi Franz,
> >Are you interested in the pmacct server hostname or the IP address of
> >the NetFlow/IPFIX/sFlow exporter? Would peer_src_ip, the IP address of
> >the flow exporter do it? Or you are collecting via libpcap or NFLOG?
> >On Mon, Aug 21, 2017 at 05:23:34PM +0200, fboehm wrote:
> >>we use pmacct to purge traffic data to a MySQL database for billing
> >>purposes. We might need to run multiple pmacct instances to monitor
> >>all relevant traffic.
> >>It would be most convenient for postprocessing if all pmacct
> >>instances could write into the same SQL tables. For example by
> >>adding an additional column with the hostname of the pmacct server.
> >>Unfortunately I only know how to assign a certain database or table
> >>to each pmacct instance. But not how to modifiy the SQL schema to
> >>support a hostname or other identifier.
> >>Kind regards,
> >>pmacct-discussion mailing list
> >pmacct-discussion mailing list
> Hi Paolo,
> At the moment we use libpcap instead of netflow. Those there is
> unfortunately no flow exporter.
> I used netflow for a while but I like to just rely on a mirrored
> switch port. I think it's easier to manage in contrast to networking
> gear with netflow support.
> pmacct-discussion mailing list
pmacct-discussion mailing list