LevelBlue Completes Acquisition of Cybereason.  Learn More

LevelBlue Completes Acquisition of Cybereason.  Learn More

Services
Cyber Advisory
Managed Cloud Security
Data Security
Managed Detection & Response
Email Security
Managed Network Infrastructure Security
Exposure Management
Security Operations Platforms
Incident Readiness & Response
SpiderLabs Threat Intelligence
View All Services
Solutions
BY INDUSTRY
BY REGULATION
BY TOPIC
Offensive Security
Solutions to maximize your security ROI
Operational Technology
End-to-end OT security
Microsoft Security
Unlock the full power of Microsoft Security
Securing the IoT Landscape
Test, monitor and secure network objects
Why LevelBlue
About Us
We reduce cyber risk and fortify organizations
Awards and Accolades
Recognition by analysts and media outlets
LevelBlue SpiderLabs
Global researchers, ethical hackers, and responders
LevelBlue Security Operations Platforms
Unprecedented security visibility and control
Security Colony
Access to cybersecurity threat protection resources
Partners
Microsoft Security
Unlock the full power of Microsoft Security
Technology Alliance Partners
Key alliances who align and support our ecosystem of security offerings
Register
Login
Resources
BLOGS
UPCOMING
MEDIA & ASSETS
NOTICES
HELP
Loading...
Loading...

LevelBlue Knowledge Base

Home » Knowledgebase » Legacy Products » Threat Analysis Reporter » INFO: TAR Bandwidth Gauges register zero activity

INFO: TAR Bandwidth Gauges register zero activity

Expand / Collapse
Show/Hide Article Tools


This article applies to:

  • Threat Analysis Reporter

Question:

TAR Bandwidth Gauges register zero activity

Reply

If the bandwidth gauges in your TAR are not moving, check the timespan value assigned to them and make sure it's not set to anything less than 5 minutes (default is 15 minutes).

The threshold for the timespan minimum time window is really determined by the environment the TAR is in, as higher volumes of traffic will require more processing time. In a high traffic traffic environment, it will take about 3 to 4 minutes for the TAR to process the volume of data that is going through it before the bandwidth gauges will display anything. Any gauges that are set for a threshold of less than this will end up showing no data. We will be looking to improve this behavior in future versions of TAR, but at this point, we don't have the functionality built in to allow TAR to automatically adjust this value according to load.
This article was previously published as:
8e6 KB 299675

To contact LevelBlue about this article or to request support:

Rate this Article:
     
Tags:

Add Your Comments


Comment submission is disabled for anonymous users.
Please send feedback to Trustwave Technical Support or the Webmaster.


Execution: 0.031. 8 queries. Compression Disabled.
Powered by InstantKB.NET