Re: [pmacct-discussion] Matching data to options with nfacctd

2017-06-08 Thread Paolo Lucente
Hi Yann, For applications, you can rely on the built-in correlation mechanism. You may run in the same issue, yes; your feedback would be valuable in seeing how wide-spreaded is the issue. This used to work. For interfaces, confirm such correlation is not currently supported; if possible, could

Re: [pmacct-discussion] Matching data to options with nfacctd

2017-06-07 Thread Yann Belin
Hi Paolo, Thanks for the reply. I'm not doing anything too fancy, only correlating two types of fields: Interfaces and Applications. - For applications, I'm using the same fields than Gilad in the GitHub issue, except that I'm doing the correlation in post processing. Since we are both using Ci

Re: [pmacct-discussion] Matching data to options with nfacctd

2017-06-06 Thread Paolo Lucente
Hi Yann, 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