EUM Data

This page is to help you understand the following: 

• the types of EUM data
• how data is collected
• where data is stored
• where data is displayed in the Controller

Types of EUM Data

Metrics

Metrics are data that reflect your application's performance. Browser RUM captures metrics using your end-users' web browsers such as timing and Ajax metrics. Mobile RUM captures metrics from mobile applications, such as crash metrics and network request metrics. You can view and analyze EUM metrics in the Metric Browser.

To learn more about EUM metrics, see the following:

• Browser RUM Metrics
• Browser Synthetic Metrics
• Mobile RUM Metrics
• Extensions and Custom Metrics

Custom Data

Browser RUM

You can add user information that is specific to your application to a browser snapshot. The information is expressed as key-value pairs. The information appears in the User Data section of the snapshot and is available for page snapshots, Ajax requests, and virtual pages. To learn how to set custom user data, see Add Custom User Data to a Page Browser Snapshot.

Mobile RUM

Mobile RUM custom data such as Info Points, Custom Timers, and Custom Metrics are considered metrics and not records stored as mobile request event data. User data is another type of Mobile RUM custom data. Modifying user data affects the current state but does not generate event records. Changes to user data can be reported, however, through network request events because user data is attached to each network request. 

To learn how to set user data, see User Data (iOS SDK) or User Data (Android SDK).

Cookies

Browser RUM uses two different kinds of short-lived cookies to help it collect data and correlate events. Neither type of cookie contains any personally identifiable information (PII) and are immediately deleted after being read.

• The ADRUM cookie: written by the JavaScript Agent, this cookie contains the referral page URL and some timing information to assist gathering First Byte Time for some browser types. When the agent loads on the subsequent page, it reads the information and then deletes the cookie. If there is no agent on that page, the cookie is deleted when the browser is closed. For privacy purposes, the URL of the referral page is hashed.
• The ADRUM_BT cookies: written by the server-side agent when the page is served from an instrumented server. These cookies help correlate browser data with related server-side performance data. 
  • ADRUM_BTa - contains the backend transaction ID as well as timing info and is used to correlates end-user experience with the health of the backend app.
  • ADRUM_BTg - contains the backend transaction ID and is used an alternative method to correlate end-user experience with the health of the backend app.
  • ADRUM_BT[1-5] - contains the business transaction numbers as well as timing and error info for the first five business transactions, such as ADRUM_BT1, ADRUM_BT2, etc.
  • ADRUM_BTs - contains a link from a browser snapshot to a server snapshot. 
  • ADRUM_BTh - only written if there was a server-side error.

If Browser RUM detects that the page is HTTPS, the cookies are HttpsOnly. 

Web Storage

Browser RUM stores key-value pairs in web storage to associate page views with a particular session and browser. The value for each key is a randomly generated ID.

The following lists the keys and the expiration time for each key-value pair:

• ADRUM_AGENT_INFO (never)
• ADRUM_CLIENTINFO (never)
• ADRUM_XD_AGENT_ID (never)
• ADRUM_XD_AGENT_INFO (1 week)

Mobile Local Storage

Mobile Agents use beacons to transmit metrics, meta data about the app, network requests, crashes, and custom data. When a beacon cannot be transmitted, the data is persisted in permanent storage within the container of the application and subject to the security configuration of the device and application. No encryption is currently being utilized. Once the network connection is restored, the beacons resume transmitting data. Because some of the data is provided by the developer's instrumentation of the app, such as breadcrumbs, user info, and the app (URLs, crash reports), some information is not explicitly collected by AppDynamics.  

Mobile RUM also locally stores a randomly generated ID for tracking sessions and license usage. The ID is stored in the Events Service.

How Data Is Stored and Retrieved

Browser RUM

Browser RUM data is stored in the Controller, the Events Service, and the EUM Server. The JavaScript Agent sends raw data to the EUM Server, where the data is verified, aggregated, and packaged every minute. The EUM Server then sends the data to the Controller and the Events Service. The Controller UI makes requests to the Controller API, which fetches data from one of the three data stores (EUM Server, Events Service, Controller). Because the Controller UI only interacts with the Controller API, it doesn't need to know where the data is stored. 

Mobile RUM

Mobile RUM data is stored in the Controller, the Events Service, and the EUM Server. The Mobile Agents send raw data to the EUM Server, where the data is verified, aggregated, and packaged every minute. The EUM Server then sends the data to the Controller and the Events Service. The Controller UI makes requests to the Controller API, which fetches data from one of the three data stores (EUM Server, Events Service, Controller). Because the Controller UI only interacts with the Controller API, the Controller UI doesn't need to know where the data is stored. 

Data Storage Details

Browser RUM

The table below shows where different Browser RUM data is stored and how long the data is retained. Resource details are only available for those browser snapshots with resource timing.

Mobile RUM

The table below shows where different EUM data is stored and how long the data is retained.

Controller Mapping of Data

Browser RUM

The table below shows the relationship between the Controller UI components and their data sources.

Mobile RUM

The table below shows the relationship between the Controller UI components and their data sources.

How to Access EUM Data

Browser RUM

In addition to accessing Browser RUM data through the Controller UI, you can also access Browser RUM data through Application Analytics and the AppDynamics APIs. 

Application Analytics includes Browser Analytics that can be used to access Browser RUM event data. If you have enabled analytics and Browser RUM, you can use Browser Analytics to view data for the following event types:

• Browser requests
• Browser sessions

The AppDynamics APIs include the Analytics Events API that you can use to access Browser RUM event data and the Metric and Snapshot API that you can use to access Browser RUM metric data.

Mobile RUM

In addition to accessing Mobile RUM data through the Controller UI, you can also access Mobile RUM data through Application Analytics and the AppDynamics APIs. 

Application Analytics includes Mobile Analytics that can be used to access Mobile RUM event data. If you have enabled Application Analytics and Mobile RUM, you can use Mobile Analytics to view data for the following event types:

• Mobile requests
• Mobile sessions
• Mobile crash reports

The AppDynamics APIs include the Analytics Events API that you can use to access Mobile RUM event data and the Metric and Snapshot API that you can use to access Mobile RUM metric data.

Data and Deployment Models

AppDynamics offers the two deployment models SaaS and on premises. You can access most Browser and Mobile RUM data from either deployment model.