The "tag" option sounds promising. I will test it.
Many thanks,
Franz
Am 2017-08-22 um 20:01 schrieb Paolo Lucente:
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
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 pos
Maybe an INSERT trigger on the MySQL table can be used to track the
database user used by the pmacct instances in order to populate an
additional field? A one-to-one mapping between instances and db users could
identify the pmacct instance that inserted the record.
Should be tested...
--
Pier Car
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?
Paolo
On Mon, Aug 21, 2017
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?
Paolo
On Mon, Aug 21, 2017 at 05:23:34PM +0200, fboehm wrote:
> Hi,
>
> w
Hi,
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
