Submit a ticketCall us

Training ClassThe Orion® Platform Instructor-led Classes

Provided by SolarWinds® Academy, these trainings will introduce users to the Orion Platform and its features, management, and navigation. These courses are suitable for users looking to discover new tips, tricks, and ways to adapt their Orion products to better suit their monitoring needs:
Deploying the Orion Platform
Configuring Orion views, maps, and accounts
Configuring Orion alerts and reports

Reserve your seat.

Home > Success Center > Netflow Traffic Analyzer (NTA) > NTA - Knowledgebase Articles > NTA reporting shows incorrect ingress and egress data

NTA reporting shows incorrect ingress and egress data

Updated October 12, 2016

Overview

When creating a report that filters out one node using the Netflow Flow History the data shown is incorrect. The ingress and egress data display values that do not exist when looking at the charts for the specific interfaces.

Environment

All NTA versions

Cause 

This happens when using the egress or ingress ID as one of the queries. Some entities are blocked or filtered out when they are unrelated to the modifier selected, which in this case is Netflow Flows by history. This is by design and if you would like these entities filtered out so they are not available to display, a feature request can be submitted. 

Resolution

  1. Submit a feature request

 

 

 

 

Last modified

Tags

Classifications

Public