Configuring a NAM Probe for ADS data generation

Applies to DC RUM 2017

A NAM Probe (old AMD) supplying data to an ADS requires more resources (mostly processor) to prepare data for the protocols reported by that server. The capacity of these NAM Probe is slightly lower, even in areas not related to analyzing traffic reported by the ADS.

To optimize processor usage for ADS data generation:

Compare your expected requirements with capacity and sizing limits, and plan lower capacity limits if an ADS is to be used.

Reduce the scope of your monitoring where possible.

Select only those pages and URLs that are useful for your analysis.

Ensure that the NAM Probe is configured so that the number of observed dimension values does not expand unnecessarily.

For more information, see Configuring NAM Probe scalability options.

Reduce the number and complexity of sequence transaction definitions.

When your monitoring configuration is complex, the NAM Probe's capacity may be significantly lower than the standard estimates. In particular, this applies to transdata performance because it depends heavily on the number and complexity of sequence transaction definitions.

Monitor the resources consumed by the v2page and page2trans processes to determine whether ADS data preparation is substantially contributing to the CPU load.

Select Diagnostics ► NAM Probe statistics and select the Resource utilization tab to display resource utilization for NAM Probes.

Monitor CPU usage and the number of dropped packets. Dropped packets signify a CPU resource problem.

Select Diagnostics ► NAM Probe statistics and select the NAM Probe processes CPU stats tab to display CPU stats for NAM Probes processes.