Per data center

You must deploy at least one

The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

instance in each data center. If a single data center has multiple tapping points or if one Collector cannot handle the traffic load, deploy additional Collector instances (one per tapping point and as many as necessary to handle the traffic load).

Recommendation

If you must deploy more than one Collector instance, use a smart tap to direct a subset of the traffic to each instance.

In multiple data centers, deploy one or more

The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

instances per data center. All Collector feeds provide data to a central

The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

instance (or set of analyzers).

Note

A single Analyzer instance can receive data from a maximum of three Collector instances.

In another location, deploy one or more Analyzer instances, one or more

The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

instances, and one

The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

instance. Add all Collector and Analyzer instances to the Console.

A multiple data-center system

depl_dcenter_multiple.png

 

Note

You can also deploy separate Analyzer instances per data center. For example, you might want to do this to view performance metrics for one geographic region separate from other regions.

Related topics

Sizing-considerations
 Deployment use cases: Per-traffic-volume
 Deployment use cases: Segment-based-deployment

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*