Hi  @Pablo_PL 

Thanks for posting here.

It is unreasonable to analyze all traffic in this way, as it would consume a large amount of resources and even affect basic network functions. It is recommended to describe the scenario in detail and specify which type of data you want to analyze and monitor.

Primary Scenario: Which category of network issues are you most urgently in need of diagnosing? (e.g., traffic taking the wrong path due to ineffective policy routing, high access latency for specific services, or load imbalance)

Target Traffic: Which part of the traffic do you wish to monitor first? (e.g., egress traffic from the data center to the internet, peering connection traffic between cross-region VPCs, or all ingress traffic for a group of web servers)

Key Information: For this traffic, aside from the source/destination addresses, what are the three most critical analysis metrics? (e.g., actual egress link, round-trip latency, or whether specific ACLs or policies were triggered)

Resource Constraints: How much resources are you able to allocate for log storage and performance overhead of this tool? (e.g., allowing no more than 1% additional CPU overhead, logs retained for 7 days)