Submit a ticketCall us

Training ClassSign up for Network Performance Monitor (NPM) and Scalability instructor-led classes

Attend our instructor-led classes, provided by SolarWinds® Academy, to discuss the more advanced monitoring mechanisms available in NPM as well as how to tune your equipment to optimize its polling capabilities. NPM classes offered:
NPM Custom Monitoring and Polling
Orion Platform Scalability

Reserve your seat.

Home > Success Center > Netflow Traffic Analyzer (NTA) > NTA - Knowledgebase Articles > Understanding Netflow charts and measurements

Understanding Netflow charts and measurements

Table of contents
Created by Eric Bryant, last modified by MindTouch on Jun 23, 2016

Views: 3,032 Votes: 2 Revisions: 6


This article provides brief information on common misconceptions/misunderstandings between charts bit rates and measurements of the amount of data transferred over a period of time. 



All NTA versions


Above the graph displays a data point at 2.9 kbps. This is a data point for the rate the total data was sent at. This should not get confused with the amount of data transferred over the period of time set for the total traffic graph. As you can see below the graph it states how much total ingress and egress bytes sent. Bytes and a per second (kbps) data point are two different measurements. 





Example Graph explained in detail:

The data in the peak of the graph is not meant to match the data in the legend of the resource. The legend below the graph is an indication of the TOTAL AMOUNT of data for that protocol that occurred between the time of 11:45am and 12:15pm. The graph is giving a visual representation of how FAST the total amount of data came in relative to the time of the graph. If you look at the legend, it says 15.4 kbytes and 6.3 kbytes, not 15.4 kbps or 6.3 kbps as the peak of those. These are values indicating two separate aspects: data size and data rate. So by looking at the chart, you can see that 21.7 kbytes (ingress and egress combined) worth of TCP based data came in one spike at a rate of 2.9kbps at the time of 11:54am. The peak information in the graph is not meant to be stating 2.9kb of total data came in at that exact time, it’s designating that it came in at a RATE or SPEED of 2.9kbps. Total data received and how fast that data arrived are not the same thing, but they are part of the same coin.





Last modified