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.

EUM Analytics Data

You can view EUM data in Application Analytics if you have an Application Analytics license separate from the EUM licenses. The EUM data found in Application Analytics consists of event data and is stored in the Events Service. The EUM Analytics data visualized in widgets is also from the Events Service.

For details about the limits and retention policy for EUM Analytics data, see the entries for Browser Analytics (SaaS), Browser Analytics (on-prem), Mobile Analytics (SaaS), and Mobile Analytics (on-prem) given on the License Entitlements and Restrictions page.

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 Security attribute is set for cookies. The Security attribute is a flag that forbids a cookie from being transmitted via an unencrypted HTTP connection.

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, metadata 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.

Controller

Events Service

EUM Server (SaaS/On-Premises)

Retention Period

Browser Metrics

✓

1 year

Browser Snapshots

✓

2 weeks

Resource Details

✓ (filesystem)

2 weeks

EUM Page Configuration

✓

✓ (filesystem)

N/A

Page View Events

✓

8 days

Ajax Events

✓

8 days

Session Events

✓

8 days

Metadata

✓

✓ (MySQL)

Indefinitely

Licenses (SaaS)

✓ (MySQL)

Indefinitely

Licenses (On-Prem)

✓ (MySQL)

Indefinitely

Mobile RUM

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

Controller

Events Service

EUM Server (SaaS/On-Premises)

Retention Period

Mobile RUM Metrics

✓

1 year

Network Request Snapshots

✓

2 weeks

Custom Data

✓

✓

1 year

Crash Analyze

✓

✓ (filesystem)

1 year

Events

✓

2 weeks

Session Events

✓

8 days

Metadata

✓

✓ (MySQL)

Indefinitely

ProGuard/dSYM Files

✓ (filesystem)

Indefinitely

Screenshot Files

✓ (S3 for SaaS, filesystem for on-prem)

8 days

Licenses (SaaS)

✓ (MySQL)

Indefinitely

Licenses (On-Prem)

✓ (MySQL)

Indefinitely

Controller Mapping of Data

Browser RUM

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