Monitoring Configuration

You can configure details relevant to monitoring charts and the monitoring data that is collected. You can configure how the data is displayed, how the traffic is analyzed for monitoring purposes, which order of resolution methods are tried when resolving IPInternet protocol addresses to hostnames, whether data is collected, and whether collected data is deleted.

For configuring how data is to display, you can specify how many items are shown in the data tables, how many items are shown in the pie charts, and how many characters to show in the URLs.

For analyzing traffic, you can specify whether to recognize traffic according to layer 7 or layer 3 definitions, and how sensitive (or aggressive) to be when attempting to recognize BitTorrent, eDonkey, Skype, and flowthe network traffic between network objects detection.

For analyzing traffic for specific application types (Application Specific Analysis Modules (ASAM)), you can specify whether to extract data from Citrix, http, and SSL traffic, whether to identify anonymous proxies in the traffic, whether to analyze VoIP traffic, whether to calculate the performance and health of connections, whether to collect connection symmetry information, and whether to log every URL seen in the traffic.

For resolving IP addresses to hostnames, you can specify which methods are tried first, second and so on: network objecta logical definition created and stored in the Exinda lilbrary, can represent any network component, DSN, NetBios name lookup, and IP address.

For collection of monitoring data, you can specify whether to collect data for subnets and virtual circuits, and whether to collect detailed records for applications, hosts, URLs, users, conversations and subnets, and whether to collect data for traffic between internal network objects.

For deleting monitoring data, you can selectively delete various types of data collected by the appliance.