Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

Home > Success Center > Netflow Traffic Analyzer (NTA) > NTA Documentation > NTA 4.4 Administrator Guide > Get started with NTA > Reasons not to export both ingress and egress NetFlow traffic data

Reasons not to export both ingress and egress NetFlow traffic data

Table of contents
No headers

Flows carrying NetFlow traffic data enter a device through an ingress interface and leave the device through an egress interface. For more information, see Monitor traffic flow directions.

If you export both ingress and egress data for all interfaces, you will get the same data twice: once as ingress data entering the device, and once as egress data as the flow leaves the device.

If you configure exporting ingress data on some interfaces and exporting egress data on other interfaces, the data shown by SolarWinds NTA may be inconsistent.

SolarWinds recommends that you configure exporting either ingress or egress data to prevent SolarWinds NTA from showing misleading traffic data.

Last modified