Great point. There are a very few cases where pmacct does the magics of
correlating actual data to options on your behalf, ie. sampling rate and
application ID. So, given the current functionality, it sounds you are
doing the right thing saving both and correlating it afterwards as part
of your post-processing. It would be great to know - here or via unicast
email - what kind of correlation you are doing.
On Tue, Jun 06, 2017 at 03:28:30PM +0200, Yann Belin wrote:
> I was reading trough recent issues on GitHub, and #137 [see link
> below] got my attention. The last comment from Paolo leads me to think
> that nfacctd can be configured to (try to) automatically match flow
> data to option table(s).
> Is it the case, or am I misreading something? Until now, I have been
> collecting data and options separately (using nfacctd_account_options)
> and had to match it afterwards via a script; such feature could make
> my life quite easier.
> Ref. https://github.com/pmacct/pmacct/issues/137
> pmacct-discussion mailing list
pmacct-discussion mailing list