Leonardo Parente

C++ does not support reflection by standard. It still a [proposal](https://meetingcpp.com/blog/items/reflections-on-the-reflection-proposals.html). We should discuss the better way to achieve that RFC. Some C++ reference libs: [Boost.PFR](https://www.boost.org/doc/libs/1_75_0/doc/html/boost_pfr.html) [Cereal](https://github.com/USCiLab/cereal) [refl-cpp](https://github.com/veselink1/refl-cpp)

@weyrick we have visor::handler and visor::input namespaces, do what is the idea of this visor::module? it would be for the abstract classes?

**Improvements questions**: on DNS Xact Will Filter we should delete transaction that will be filtered out? I think So..

> This is in Draft, is it ready for review? No, It is not. Things changed a lot on DnsHandler, rebase this will be difficult. I will start over.

### **Premises** 1. **matcher** is the one that will look all or part of the traffic and call InputEventProxy `send_metadata` 2. **matcher** needs to implement call logic and validate its...

 Based on image above we have the call hierarchy for **DNS UDP** traffic: 1. **_All Traffic Policy DNS Handler_** will be the **matcher**, so it register itself as...

> is this still dependent on the order of the policies? i also cannot wrap my head around the names of the concepts here, i will try to think of...

@weyrick Just noticed that with that approach we loose the feature to track `filtered out counter` because the function that track it is never called

@karlTH Will it have support to MQTT?

We should only track the payload size on pktvisor. Storage metrics size can vary based on intermediary tools