Re: [pmacct-discussion] Only meaningful custom primitives should pick the value

2020-01-20 Thread Paolo Lucente
Hi, You could put the port filter in a pcap_filter and have two pmacctd, one reading http traffic, one reading dns traffic and each configured to pick up and export the relevant primitives. Would that work for you? Paolo On Fri, Jan 17, 2020 at 11:45:26AM +0530, HEMA CHANDRA YEDDULA wrote: >

Re: [pmacct-discussion] Only meaningful custom primitives should pick the value

2020-01-16 Thread HEMA CHANDRA YEDDULA
Hi, Thanks for the prompt reply. I think there is some misinterpretation of the scenario.I'm trying to explain it litte more explicitly We want to add some primitives defined by us with our PEN value. And the primitives are of different protocols like http and dns in same template. In our

Re: [pmacct-discussion] Only meaningful custom primitives should pick the value

2020-01-16 Thread Paolo Lucente
Hi, If you define certain primitives, those not present in the parsed flow entry should be indeed left blank. If that is not the case, then it's a bug and i'd like to ask you for a way to reproduce the issue (so your config along with a brief capture (template + data packets) of your data.

[pmacct-discussion] Only meaningful custom primitives should pick the value

2020-01-15 Thread HEMA CHANDRA YEDDULA
Hi, I have a scenario where we are planning to add custom primitives that includes fields across different protocols like http_request_host, http_response_code, sip_request_uri and sip_status_code. In the existing version, if they are defined to be picked up from payload, then all four of