CAS ► Settings ► CAS configuration, section User options

CAS ► Settings ► CAS configuration, section User activity details and server statistics on demand 

The number of monitored users is usually the most important factor for the overall number of sessions. If the CAS is deployed in a large environment (such as more than 50,000 users), do not store single-user information in the CAS database. Keep the number of unique users that the CAS is tracking in its database below 50,000. This number includes aggregated and individual users.

On the Central Analysis Server Configuration screen:

  • In the User options section, choose a CAS user aggregation mode.
  • In the User activity details and server statistics on demand section, indicate whether to enable on-demand access to user activity details and server statistics.

User options

Important:

  • If you intend to aggregate user data across multiple CAS instances in a cluster and want to manage the reports centrally, use the cluster configuration to modify synchronization options. For more information, see Cluster Configuration.

  • All autodiscovered clients are aggregated, regardless of any other aggregation settings. If a client IP address is private, it is aggregated by subnet, not by site, for both autodiscovered and user-defined software services.

Track user IP addresses (FE mode)

FE mode records each client IP address separately (it ignores recognized user names and reports users with IP-address resolution).

This mode consumes the most resources and significantly increases the database size. It is good for intranet sites with limited numbers of clients, coming from a limited IP address space of the internal network, and sending no information on actual website user names (no login to the website).

Remember: All autodiscovered clients are aggregated, regardless of any other aggregation settings. If a client IP address is private, it is aggregated by subnet, not by site, for both autodiscovered and user-defined software services.

Track users with identifiers, aggregate other users (ISP mode)

In this mode, you track users with defined user names and aggregate other users. The ISP modes record each user name separately. User name recognition from HTTP logins must be enabled on the AMD.

ISP mode enables you to count user IP addresses that are aggregated as single users.

Remember: All autodiscovered clients are aggregated, regardless of any other aggregation settings. If a client IP address is private, it is aggregated by subnet, not by site, for both autodiscovered and user-defined software services.

  • also track IP addresses from selected ranges
    Record each client IP address separately.
  • also count user IP addresses that are aggregated (ISP Extended mode)
    Select also count user IP addresses that are aggregated to see the number of unique client IP addresses for user aggregates.
    Use the ISP mode for websites with required login and limited numbers of website users (for example, e-commerce secure sites). Traffic generated by clients that have not been identified (no user name is available) is aggregated into user-defined sites, AS instances, or CIDR blocks. However, if you specify user IP addresses and select also track IP addresses from selected ranges (ISP Extended mode) you will track users that do not have defined user names.

For more information, see Limitations of ISP Mode User Aggregation.

Aggregate all users but count distinct user identifiers (PVU mode)

In this mode, all clients from the same Autonomous System (AS) or CIDR block or subnet are treated as a single user, but the number of unique, non-aggregated users is also provided (for named users in the default configuration). The PVU mode is appropriate for large and very large Internet-facing websites, when knowledge of the number of unique site visitors is needed. The CAS maintains the top N most active AS instances or CIDR blocks as identified client sites (user substitutes), and it rolls up other clients into a single All Other Clients category. Although users are aggregated, the CAS provides an accurate count of actual unique users of the monitored website. Users are counted before aggregation is applied, and the real user count is provided as a metric on CAS reports.

  • To count users that do not have defined user names, specify user IP addresses and select also count user IP addresses from selected ranges. Unique users are identified on AMDs based on cookies or HTTP headers that identify users.
    Remember: All autodiscovered clients are aggregated, regardless of any other aggregation settings. If a client IP address is private, it is aggregated by subnet, not by site, for both autodiscovered and user-defined software services.

For more information, see Limitations of PVU Mode User Aggregation.

Aggregate all users (PV mode)

In this mode all clients from the same AS or from the same CIDR block are counted as a single user. Use the PV mode for large, Internet-facing websites. The CAS maintains the top N most active AS instances or CIDR blocks as identified client sites (user substitutes), and it rolls up other clients into a single All Other Clients category.

User activity details and server statistics on demand

This configuration option allows the CAS to bypass the database and store user-activity details separately on disk. This option is useful when user details are not needed on a regular basis but need to be available for occasional inspection. With this option configured, aggregated values are still shown on CAS reports, and user-level details are accessed through drill-downs.

If this option is used in the ISP Extended mode, all user information is saved. If this option is used in the PVU mode, user information is saved for all distinct user identifiers and optionally also for selected IP address ranges. (All autodiscovered clients are aggregated, regardless of any other aggregation settings. If a client IP address is private, it is aggregated by subnet, not by site, for both autodiscovered and user-defined software services.)

Note that User activity details and server statistics on demand mode imposes a limitation in filtering. When you drill down from the All Users report to the List of users (on demand) report, you lose the contextual application and tier filters.

Consider using this configuration option as a way to reduce database size and memory usage, assuming that you accept user details to be available through drill-downs only, and aggregates being present on higher-level reports. Remember that – subject to traffic characteristics – large amounts of disk storage may be required for user data. For more information, see Enabling user activity details and server statistics on demand and List of Users On Demand Report.

Clients from each AS or CIDR block are divided into four categories based on their server realized bandwidth, making four virtual client entries per AS or CIDR block: modem, broadband, T1, or LAN.

DC RUM creates user aggregates based first on manual site definitions, and then on CAS configuration (the Base user aggregation on option on the Central Analysis Server Configuration screen).

In addition to user aggregations, the CAS also builds a hierarchy of client (user) sites that are used for roll-ups and are a reflection of the user topology, for example, enterprise network structure, geographical or departmental hierarchy. Site hierarchy is derived from the BGP routing tables (AS and CIDR blocks) or based on manual site definitions. Define the hierarchy under the Base automatic sites on option on the Central Analysis Server Configuration screen.

User aggregation modes are related to the site model. Your choice of a particular user aggregation mode determines how the sites will be maintained. It is possible to mix user aggregation modes on two separate CAS instances. For example, aggregate website users from the Internet into a single user, while monitoring users from the corporate intranet individually.

  • No labels