This page describes how to interpret the details of your Analytics license. The information is split between Infrastructure-based Licensing and Agent-based Licensing. To see a complete list of licenses and packages, see License Entitlements and Restrictions

Licensing for Analytics

Analytics licenses differ depending on what licenses you purchase. Under the Infrastructure-based Licensing model, Analytics licenses are part of monitoring packages, except for Log Analytics, which is a separate license. Under the Agent-based model, each Analytics agent is licensed separately. Learn more about Licensing.

Types of Licenses

There are three types of licenses associated with Analytics:

  1. Browser and Mobile Analytics (part of Real User Monitoring Peak)
  2. Transaction Analytics (part of the Enterprise package)
  3. Log Analytics (part of Log Analytics Pro)

See License Entitlements and Restrictions for more information on each license.

With a Browser Synthetic Pro license, you do not need an Analytics license to view Synthetic session data.

How Licenses Are Consumed

  • The Java Agent collects Transaction Analytics data. The Transaction Analytics license (as part of the Enterprise license package) is consumed through the Java Agent (as part of the Analytics Agent). If the Agent does not have an Enterprise license allocated, the agent will not be able to report Transaction Analytics data.
  • The Analytics Agent does not consume any licenses. The Controller account information configured in the Analytics Agent is used for the periodic health check and log configuration sync; whether or not the account has IBL licenses provisioned does not matter.

Accounts and Licenses

  • The Global Account Name (GAN) configured in the Analytics Agent is used for request authentication and rate-limiting in the Events Service, and is not related to license allocation.
  • The account configured in the Java Agent must have enough licenses, and the agent should acquire the license in the configuration sync.

Overages

Analytics does not support overages. Cisco AppDynamics stops capturing analytics data once your limit has been reached.

Disable Transaction Analytics License Consumption

When the analytics is disabled using the disable-dynamic-services node property, it can still consume the transactional analytics license. 

To disable analytics service at the node level:

  1. Log in to the Administrator Console with the administrator root password.
  2. Select Accounts.
  3. Double-click the account for which you want to disable the analytics service.
  4. In the Account properties section, click + Add Property.
  5. In the left dialog, enter NODE_LEVEL_ANALYTICS_DISABLE_FLAG.
  6. In the right dialog, enter true.
  7. Configure the disable-dynamic-services node property.

    It may take approximately ten minutes to disable the analytics service.

Types of Licenses

There are four types of licenses associated with Analytics:

  1. Transaction Analytics 
  2. Log Analytics
  3. Browser Analytics
  4. Mobile Analytics

See License Entitlements and Restrictions for more information on each license.

With a Browser Synthetic Pro license, you do not need an Analytics license to view Synthetic session data.

Overages

Analytics does not support overages. Cisco AppDynamics stops capturing analytics data once your limit has been reached.