EUM Accounts, Licenses, and App Keys

This page covers account and licensing information for End User Monitoring (EUM).

View License Usage

To view your EUM license consumption in the Controller, go to the gear icon > License.

Overages

If your license does not allow overages, AppDynamics stops reporting metrics after your license limit has been reached. If your license does allow overages and your usage exceeds the limit, AppDynamics continues reporting EUM metrics and bills you for the overages at the unit rate stipulated by your license agreement.

License Key

If you have at least one EUM license type, you have an EUM Account, which has a name and a license key associated with it. This is the unique identifier that AppDynamics uses to associate EUM data to your account. You only need to know this information for troubleshooting purposes. The same key applies to all four EUM services. However, each product has its own types and metrics for allowed usage.

EUM App Key

This is the unique identifier that AppDynamics uses to associate end user data to specific EUM applications. Each EUM application will be associated with one EUM App Key. For your applications to be monitored, they will need to include the EUM App Key when reporting data. The EUM App Keys are also associated with an EUM account name and license key.

Changing the license key does not affect existing EUM App Keys.

License Optimization and Usage Periods

For EUM license metric definitions and data retention, see License Entitlements and Restrictions.

EUM License	License Optimization	Usage Period
Real User Monitoring	See Browser and Mobile RUM rows below.	See the Browser and Mobile RUM rows below.
Browser RUM	If the value of Pageviews is greater than Pageviews Allocated and your license allows overages, you are incurring overage charges. If you need to stop incurring overage charges, you can disable Browser RUM to stop end user monitoring and stop Pageviews from being charged (once disabled, expect a delay of approximately one minute).	The Browser RUM usage period is per year, even if you have a multi-year license. The meter resets every year based on the expiration of your license agreement. For example, if your license expires at 12:00pm PST on May 1, 2020, your usage period resets every year starting 12:00pm PST on May 1, 2021.
Mobile RUM	License consumption is affected when you have one instrumented application installed on multiple devices, multiple applications on the same device, or uninstalls followed by reinstalls: If you install one instrumented application on two devices within a month, each device uses one Monthly Active Agent. If you uninstall and then reinstall an instrumented application multiple times within a month, each reinstall uses one Monthly Active Agent. If you install two different instrumented applications on the same device within a month, each instrumented application consumes one Monthly Active Agents, so. Through SDKs, you can customize application instrumentation to choose which agents send data. For further instructions, see the following: Customize the Android Instrumentation Customize the iOS Instrumentation Customize the Xamarin Instrumentation Customize the Cordova Instrumentation	The Mobile RUM usage period begins and the meter resets on the first day of each month at 12:00pm PST. When your license consumption reaches 90% of your Monthly Active Agent allocation, you will see a warning in the Mobile RUM dashboard.
Synthetic	To help you optimize the use of your Synthetic Agent license, keep the following in mind: Synthetic jobs are measured in terms of the time it takes to actually run the test in AppDynamics systems. Because it is not possible to know in advance how long a given test may take, you can set a timeout value when you create the job. If the job times out, you receive partial results. Once you have used up your monthly allotment, all synthetic jobs are paused until the following month. If there is a problem accessing a site, such as receiving a 5xx error, the system automatically runs the job again. You are charged for these retests. If you see a session with the status INTERNAL_ERROR, this means there is a problem with AppDynamics infrastructure, and you will not be charged, even if the session contains partial results. Adjusting synthetic job configurations, such as the number of browser types, frequency, and duration, may have an impact on license consumption. To gauge estimated consumption in the Controller, create a new job and see the section Set a Timeout (step 6). Locations are user-defined. You can add multiple servers (agents) to a location to increase capacity, and this does not impact your license.	The usage period begins and the meter resets on the first day of each month at 12:00pm PST.
IoT	License consumption is based on Application Instances. We recommend that you register each Application Instance and each device so that you can correlate data with each data source. To reduce license consumption, you can register just one device with multiple Application Instances, or one Application Instance on multiple devices. However, in doing so, AppDynamics cannot differentiate data, such as errors, for each application instance or device unless each one is registered.	The usage period begins and the meter resets on the first day of each month at 12:00pm PST. The usage period for IoT is always the current month, even if you have a multi-year license.