This is a combination of dst_addr and l4_dst_port.

The target IP:Port tuple for this flow record. The target Autonomous System Name for this flow record. The target Autonomous System Number for this flow record. The target IP address for this flow record.

The display name of the sampling device for this flow record. Common examples include http, ssh, and ftp. This is derived from the lowest numeric value from l4_dst_port and l4_src_port. The class of program generating the traffic in this flow record. Visualize your network performance data in New Relic. > Add more data > Network > Network Flows to set up network flow data monitoring. Scroll down until you see Network and click Network Flows.įollow the steps outlined in the guided installation process. Set up network flow data monitoring in New Relic Deciding whether to run more small containers to distribute load or fewer large containers to consolidate management is a matter of personal preference. When planning your strategy for collecting network flows at scale, New Relic recommends 1 CPU per 2000 flows-per-second (120,000 flows-per-minute). When running the ktranslate container, you will specify which major type you want to monitor using the -nf.source option. Network flow monitoring supports the four primary types of network flow data and their derivatives. Here's how to configure network flow data collection in some devices:Ĭheck the network security prerequisites for network flow.

Configured network devices to send flow data to the host running the ktranslate docker container.

Ability to launch new containers via command line.Network access as defined in the network prerequisites.Access to install/remove applications and services.Don't have one? Sign up for free! No credit card required. Add network flow data Prerequisites and supported types of network flow data New Relic prerequisites

Network flow analyzer