NetResident - Network Content Monitoring Tool

Prev Page Next Page
System Requirements
What Network Content NetResident Can Analyze
What’s New in NetResident 3.0
NetResident Architecture
Deploying the Application
Before You Begin: Network Visibility
Step 1: Deploying the NetResident Service and Console
Step 2: Deploying NetResident Agents
Ensuring Connectivity Between the System Components
Tips and Tricks
Setting Up the Database
Step 1: Creating a New Database and Configuration File
Step 2: Selecting an SQL Server
Step 3: Selecting a Database Location and Name
Step 4: Setting Database Access Token
Step 5: Summary
Working with NetResident
Understanding the Difference Between the Display and Capture Filters
Remote Connections
Adding Exceptions to NetResident Agents
Manual SQL Server Installation
Analyzing Imported Capture Files
Frequently Asked Questions
Sales and Support

Understanding the Difference Between the Display and Capture Filters

Network content captured and analyzed by NetResident may be filtered on two levels:

· Display filter: You may apply this filter to the data that have already been captured. For example, if NetResident has been running for a week and you want to focus only on the events that occurred last Sunday, you can use the Filter tab on the Events page to set the specific date. This will allow you to temporarily discard the events that took place on other days. Now, if you want to focus on the events that occurred last Monday, you can simply change the filter to see the events for another day.
· Capture filter: You may use this filter to limit the type of events that are captured by NetResident. By default, NetResident captures and stores all the events that it can analyze, such as e-mails, Web pages, and IM chat sessions. However, some users may not want to capture and store all of this network content in order to decrease the database size and improve overall application performance. For example, you may want to completely exclude FTP file transfers. This can be done on the Agents and Service tabs of the Connections page, where you can find the Capture Options button. Use it to select the types of protocols you want the application to capture.

The difference between these two filter types is that in the case of using the display filter, all of the events are still stored in the database, and you can use the display filter to select only those events that are currently of interest to you. In the case of using the capture filter, the excluded events are lost forever; for example, if you disabled capturing FTP file transfers some time ago, you cannot restore the missed events by enabling the capturing of FTP file transfers again.