Submit a ticketCall us

Don’t fall victim to a ransomware attack
Backups are helpful, but sometimes that’s not enough to protect your business against ransomware. At our live webcast we will discuss how to protect against ransomware attacks with SolarWinds® Patch Manager and how to leverage log data to detect ransomware. Register now for our live webcast.

Home > Success Center > Netflow Traffic Analyzer (NTA) > Are there any differences in the way CBQoS data are handled

Are there any differences in the way CBQoS data are handled

Table of contents

Updated January 12, 2017

Overview

Are there any differences in the way CBQoS data are handled?

 

Environment

  • NTA 4.x

Detail

There is no fundamental change in the way CBQoS data is handled, between 3.x and 4.x: In both, the default polling period is 300 sec, and the CBQoS data are retained for the configured retention period.

 

The difference is in the displaying, because NTA 3.x was aggregating the CBQoS data consistently with the Flow data, in order to provide chart consistency. In NTA 4.x, the CBQoS aggregation has been removed in order to show as-polled data. It will therefore show more granular data than 3.x, even if the polling and retention period remains the same as in 3.x (no database sizing difference due to CBQoS between 3.x and 4.x).

 

 

 

Last modified
10:35, 12 Jan 2017

Tags

Classifications

Public