Configuring ADS scalability options

Applies to DC RUM 2017

Select an ADS model based on page load volume and your main reporting objectives.

Small website

Regardless of the page load volume, use the Small Website option if your main objective is to have fast hit-level detail reports for more than the last few hours. This option is designed for low-page load volumes, however, and may not perform well with high volumes. If page load volume is high, consider using data filtering to further limit the analyzed data to only those transactions and URLs that are most significant.

Large website

Use the Large Website option when page load volume is high and if your main objective is to use fault domain isolation or sequence transaction reporting.

The ADS stores a separate record for each page load and uses no client-level aggregation, so its capacity depends only on the number of individual page loads and measured hit loads. The ADS always stores the client IP address and identifies the user name. This enables identification of each page and page hit load separately for each user.

Configuration screen

To configure the main ADS scalability options:

Select the mode of operation of the report server: Small Website or Large Website.

For more information, see ADS Basic Configuration Settings.

Set the cut-off limit for the number of operations per day.

We recommend that you set the limit of the number operations per day. The option is provided on the Scalability screen.

Use the cut-off value to avoid overloading the system above the limits you expect it to operate within. The suggested default values for small and large website models will appear, as you change between the two configuration settings.

Fine-tune the server configuration settings. There are a number of configuration settings you can adjust to meet your monitoring objectives.

Filter data at the report server level.

Reconfigure the ADS to selectively read from the NAM Probe and extract only the data related to specified servers or clients defined by IP ranges. Note that this filtering is secondary to filtering done at the NAM Probe level, where you can specify which data is to be sent to the report server.