EUM データ

Metric Data

Metrics are data that reflect your application's performance. Browser RUM captures metrics from browser applications, 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:

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

Custom Data

Browser RUM

You can add specific user information from a browser snapshot of your application. The information is expressed as key-value pairs, 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 stored as mobile request event data. User data is another type of Mobile RUM custom data. Custom user data can be reported 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).

EUM Analytics Data

You can view EUM data in Analytics if you have a Real User Monitoring Peak license. The EUM Analytics data consists of event data and is stored in the Events Service and visualized in widgets. EUM Analytics provides data for these event types:

• Browser Requests Event Data
• Browser Sessions Event Data
• Mobile Requests Event Data
• Mobile Sessions Event Data
• Mobile Crash Report Event Data
• Synthetic Sessions
• Connected Device Data

Cookies for Browser Applications

Browser RUM uses two different kinds of short-lived cookies for the JavaScript Agent to collect data and correlate events. Both types of cookies do not contain any personally identifiable information (PII) and are immediately deleted after being read.

• ADRUM cookie: Written by the JavaScript Agent, this cookie contains the referral page URL and some timing information to assist in 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.
• 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 (Business Transactions).
  • 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 as 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

    注: 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.
• SameSite cookies: Provides the JavaScript Agent access to ADRUM_BT cookie to maintain Business Transaction correlation. When SameSite cookies are present, the agent has access to the ADRUM_BT cookie with Business Transaction data. Without SameSite cookies, the agent cannot parse Business Transaction data in the cookie sent from the application server. This is because the agent is loaded from a different domain than the browser website.

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, app metadata, 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 Splunk AppDynamics.

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