Submit a ticketCall us

Cloud Workloads: Meet Your New Hybrid IT Reality
Have you found yourself in that evolving, hybrid IT grey area and wondering if cloud workloads are now part of your purview? And if so, will monitoring cloud workloads require a new set of dedicated cloud monitoring tools? Your answers: yes, they should be, and no, they don’t.

Find out how SolarWinds® Server & Application Monitor (SAM) can help you monitor your cloud workloads side by side with your on-premises workloads. Register Now.

Home > Success Center > Netflow Traffic Analyzer (NTA) > 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. Create a custom table.
  2. Select Netflow Flow By Interface History. You will only be able to use the columns for that Orion Object (Ingress Bytes, Egress Bytes, NodeID and InterfaceID).

 

 

 

 

Last modified

Tags

Classifications

Public