User action events capture user-initiated actions within the application, providing insights into user behavior and interaction patterns.
A mobile user action represents a significant mobile frontend operation and its downstream effects. Dynatrace RUM groups the triggering interaction together with the resulting requests and navigations into a single user action event. Only supported by OneAgent for Mobile.
This query searches for all OneAgent for Mobile user actions.
fetch user.events| filter characteristics.has_user_action| filter dt.rum.agent.type == "android" OR dt.rum.agent.type == "ios"
| Attribute | Type | Description | Examples |
|---|---|---|---|
| string | experimentalFixed value |
|
| boolean | stableFixed value |
|
| boolean | stableAdditional characteristic: If set to |
|
| Attribute | Type | Description | Examples |
|---|---|---|---|
| uid | experimentalA random ID that is generated for every user action. The |
|
| string | **deprecatedThe attribute |
|
| uid | experimentalA unique identifier for user action grouping. The |
|
| string | experimentalA human-readable version of |
|
| uid | experimentalThe |
|
| uid | experimentalThe |
|
| long | experimentalThe number of hard navigations that happened during the lifespan of the user action. |
|
| long | experimentalThe number of soft navigations that happened during the lifespan of the user action. |
|
| long | experimentalThe number of navigations that happened during the lifespan of the user action. Includes all detected navigations, regardless of whether the corresponding event may be canceled via the modify event API later. Only supported by OneAgent for Mobile. |
|
| long | experimentalThe number of DOM mutations during the lifespan of the user action. |
|
| long | experimentalThe number of requests that were pending when the user action finished. |
|
| long | experimentalThe number of requests to a data URL during the lifespan of the user action. |
|
| long | experimentalThe number of requests during the lifespan of the user action. |
|
| long | experimentalThe number of resources loaded during the lifespan of the user action. |
|
| long | experimentalThe number of resources loaded during the lifespan of the user action split by initiator type, for example, |
|
| string | experimentalThe reason why the user action was completed. |
|
| string | experimentalThe user action type. |
|
user_action.complete_reason MUST be one of the following:
| Value | Description |
|---|---|
| The user action was closed because the app was moved to the background. Only supported by OneAgent for Mobile. |
| The user action was normally completed. |
| The user action was completed using the Dynatrace API. |
| The user action was interrupted by a new user action started with the Dynatrace API. |
| The user action was interrupted by a new auto-captured user action. |
| The user action was closed because the page was left. Only supported by RUM JavaScript. |
| The user action timed out. |
user_action.type MUST be one of the following:
| Value | Description |
|---|---|
| The user action was reported via the Dynatrace API. |
| The user action was triggered by an app start. Only supported by OneAgent for Mobile. |
| The user action was triggered by a hard navigation (full page load). Only supported by RUM JavaScript. |
| The user action was triggered by a mobile navigation. Only supported by OneAgent for Mobile. |
| The user action was triggered by a user interaction, followed by an XHR or fetch request. |
| The user action was triggered by a soft navigation that led to a view change. Only supported by RUM JavaScript. |
| Replaced with |
User interaction fields are only present if the user action was triggered by a user interaction.
| Attribute | Type | Description | Examples |
|---|---|---|---|
| string | experimentalType of action performed by the user. |
|
| string | experimentalCustom name of the element. Filled by the |
|
| string | experimentalUser interface element name. Captured by precedence of |
|
| string | experimentalField used to fill |
|
| string | experimentalUser interface element type. For web, it's the tag name. For mobile, it's the name of, for example, the controller or fragment |
|
| Attribute | Type | Description | Examples |
|---|---|---|---|
| long | experimentalThe total number of errors that are observed. |
|
| long | experimentalThe total number of exceptions that are observed, including exceptions that are not captured. |
|
| long | experimentalThe number of HTTP request errors with an |
|
| long | experimentalThe number of HTTP request errors with an |
|
| long | experimentalThe number of HTTP request errors with an |
|
| long | experimentalThe number of errors not related to HTTP status codes—for example, timeout or connectivity errors (Android) or other failed-request errors such as WebSocket failures (iOS). |
|
The basic attributes for all user events are defined in the user event base model.
A user action represents a significant frontend operation and its downstream effects. Dynatrace RUM groups the triggering event, for example the user interaction, together with the resulting requests and DOM mutations into a single user action event. Only supported by RUM JavaScript.
This query searches for all RUM JavaScript user actions.
fetch user.events| filter characteristics.has_user_action| filter dt.rum.agent.type == "javascript"
| Attribute | Type | Description | Examples |
|---|---|---|---|
| string | experimentalFixed value |
|
| boolean | stableFixed value |
|
| boolean | stableAdditional characteristic: If set to |
|
| Attribute | Type | Description | Examples |
|---|---|---|---|
| uid | experimentalA random ID that is generated for every user action. The |
|
| string | **deprecatedThe attribute |
|
| uid | experimentalA unique identifier for user action grouping. The |
|
| string | experimentalA human-readable version of |
|
| uid | experimentalThe |
|
| uid | experimentalThe |
|
| long | experimentalThe number of hard navigations that happened during the lifespan of the user action. |
|
| long | experimentalThe number of soft navigations that happened during the lifespan of the user action. |
|
| long | experimentalThe number of navigations that happened during the lifespan of the user action. Includes all detected navigations, regardless of whether the corresponding event may be canceled via the modify event API later. Only supported by OneAgent for Mobile. |
|
| long | experimentalThe number of DOM mutations during the lifespan of the user action. |
|
| long | experimentalThe number of requests that were pending when the user action finished. |
|
| long | experimentalThe number of requests to a data URL during the lifespan of the user action. |
|
| long | experimentalThe number of requests during the lifespan of the user action. |
|
| long | experimentalThe number of resources loaded during the lifespan of the user action. |
|
| long | experimentalThe number of resources loaded during the lifespan of the user action split by initiator type, for example, |
|
| string | experimentalThe reason why the user action was completed. |
|
| string | experimentalThe user action type. |
|
user_action.complete_reason MUST be one of the following:
| Value | Description |
|---|---|
| The user action was closed because the app was moved to the background. Only supported by OneAgent for Mobile. |
| The user action was normally completed. |
| The user action was completed using the Dynatrace API. |
| The user action was interrupted by a new user action started with the Dynatrace API. |
| The user action was interrupted by a new auto-captured user action. |
| The user action was closed because the page was left. Only supported by RUM JavaScript. |
| The user action timed out. |
user_action.type MUST be one of the following:
| Value | Description |
|---|---|
| The user action was reported via the Dynatrace API. |
| The user action was triggered by an app start. Only supported by OneAgent for Mobile. |
| The user action was triggered by a hard navigation (full page load). Only supported by RUM JavaScript. |
| The user action was triggered by a mobile navigation. Only supported by OneAgent for Mobile. |
| The user action was triggered by a user interaction, followed by an XHR or fetch request. |
| The user action was triggered by a soft navigation that led to a view change. Only supported by RUM JavaScript. |
| Replaced with |
| Attribute | Type | Description | Examples |
|---|---|---|---|
| boolean | experimentalInteraction is genuine from real user and not a synthetic event. |
|
| string | **deprecatedReplaced with |
|
| string | experimentalType of action performed by the user. |
|
| string | experimentalCustom name of the element. Filled by the |
|
| string | experimentalName of the element taken from the following fields by priority: |
|
| string | experimentalField used to fill |
|
| string | experimentalUser interface element type. For web, it's the tag name. For mobile, it's the name of, for example, the controller or fragment |
|
| Attribute | Type | Description | Examples |
|---|---|---|---|
| string | experimentalThe navigation type according to the W3C navigation timing. Only available for hard navigations. |
|
| Attribute | Type | Description | Examples |
|---|---|---|---|
| string | experimentalOSI Application Layer or non-OSI equivalent. This is a mandatory field for request user events. |
|
| Attribute | Type | Description | Examples |
|---|---|---|---|
| string | experimentalThe URI domain component. This is extracted from |
|
| string | experimentalThe URI fragment component. This is extracted from |
|
| string | experimentalAbsolute URL describing a network resource according to RFC3986. OneAgent for Mobile removes the optional user information subcomponent. This is a mandatory field for request user events.Tags: |
|
| string | experimentalThe URI path component. This is extracted from |
|
| string | experimentalThe provider type for the host name of |
|
| string | experimentalThe URI query component. This is extracted from |
|
| string | experimentalThe URI scheme component identifying the used protocol. This is extracted from |
|
| Attribute | Type | Description | Examples |
|---|---|---|---|
| uid | experimentalA unique identifier for a span within a trace. The |
|
| uid | experimentalA unique identifier for a trace. The |
|
| boolean | experimentalFlag indicating whether the trace was recorded. If set to |
|
| Attribute | Type | Description | Examples |
|---|---|---|---|
| string | experimentalIndicates if and why Dynatrace RUM set the W3C Trace Context headers on the request. |
|
| string | experimentalIndicates if and why RUM JavaScript received trace information from OneAgent via the browser's performance API ( |
|
request.trace_context_hint MUST be one of the following:
| Value | Description |
|---|---|
| Trace Context headers were set using the Dyntrace API. |
| Trace Context headers were not set in the customer code using the Dyntrace API, therefore it's expected that the header is not set. |
| Trace Context headers were not set because the request is a cross-origin request. |
| Trace Context headers were not set for the request because the feature is disabled. |
| Trace Context headers were not set because the request is excluded by configuration. |
| Trace Context headers were not set because the |
| Trace Context headers were set based on the request's |
| Trace Context headers were set because the request is included by configuration. |
| Dynatrace RUM generated new and replaced the existing Trace Context headers because the existing |
| Trace Context headers were not set because the maximum length for the tracestate entry was exceeded. |
| Trace Context headers were not set because mandatory values were not available to Dyntrace RUM. |
| Trace Context headers were not set because the request is not an HTTP request. |
| Trace Context headers were not set because the initial configuration was not received. |
| Trace Context headers were not set for the request. |
| Trace Context headers were set for the request. |
request.server_timing_hint MUST be one of the following:
| Value | Description |
|---|---|
| RUM JavaScript ignored invalid trace information. |
| RUM JavaScript received trace information that doesn't match the Trace Context headers. |
| No trace information available. |
| Server-Timing not available. |
| Server-Timing not available due to an insecure HTTP connection. The |
| RUM JavaScript received valid trace information. |
| Attribute | Type | Description | Examples |
|---|---|---|---|
| long | experimentalThe number of CSP rule violations. |
|
| long | experimentalThe number of exceptions that are observed, but which are not captured due to error capture limits. |
|
| long | experimentalThe total number of exceptions that are observed, including exceptions that are not captured. |
|
| long | experimentalThe number of HTTP request errors with an |
|
| long | experimentalThe number of HTTP request errors with an |
|
| long | experimentalThe number of HTTP request errors with an |
|
| Attribute | Type | Description | Examples |
|---|---|---|---|
| double | stableThe |
|
| duration | stableThe |
|
| duration | stableThe |
|
| duration | stableThe |
|
| duration | stableThe |
|
The Largest Contentful Paint (LCP) attributes contain additional information about the captured web_vitals.largest_contentful_paint.
| Attribute | Type | Description | Examples |
|---|---|---|---|
| string | experimentalThe status information for LCP. |
|
| long | experimentalThe number of LCP updates during the entire lifespan. |
|
| double | experimentalThe value of the LCP object's |
|
| string | experimentalIf the element is an image, the request URL of the image. |
|
| double | experimentalThe value of the LCP object's |
|
| double | experimentalThe value of the LCP object's |
|
| long | experimentalThe intrinsic size of the element representing its area on the screen. The value is equal to the element's width multiplied by its height, in pixels. |
|
| string | experimentalThe element's ID. |
|
| string[] | experimentalThe element's xpath. Might be missing, for example, for element's that are inside a shadow DOM. |
|
| string | experimentalThe element's tag name. Might be missing, for example, for element's that are inside a shadow DOM. |
|
| double | experimentalThe element's render delay, that is the time between when the element finishes loading and when it is fully rendered. The unit is milliseconds. Only available if a resource timing is available for the element. |
|
| double | experimentalThe resource's load delay, that is the time between |
|
| double | experimentalThe resource's load duration, that is the total time it takes to load the resource. The unit is milliseconds. Only available if a resource timing is available for the resource. |
|
lcp.status MUST be one of the following:
| Value | Description |
|---|---|
| LCP is not reported because the browser tab was loaded in the background. |
| LCP is not reported because capturing of page and view summaries is disabled (only used for activity events). |
| LCP is not reported because the browser tab was in the background before the value could be reported. |
| LCP is reported. |
The First Input Delay (FID) attributes contain additional information about the captured web_vitals.first_input_delay.
| Attribute | Type | Description | Examples |
|---|---|---|---|
| string | experimentalThe status information for FID. |
|
| string | experimentalThe document's loading state recorded at the point in time when the FID was captured. |
|
| double | experimentalThe value of the FID object's |
|
| double | experimentalThe value of the FID object's |
|
| string | experimentalThe value of the FID object's |
|
| double | experimentalThe value of the FID object's |
|
| double | experimentalThe value of the FID object's |
|
| double | experimentalHow long it took for the event handler to execute. This is calculated as |
|
| boolean | experimentalThe value of the FID object's |
|
| string[] | experimentalThe element's xpath. Might be missing, for example, for element's that are inside a shadow DOM. |
|
| string | experimentalThe element's tag name. Might be missing, for example, for element's that are inside a shadow DOM. |
|
fid.status MUST be one of the following:
| Value | Description |
|---|---|
| FID is not reported because capturing of page and view summaries is disabled (only used for activity events). |
| FID is not reported because there was no user interaction. |
| FID is not supported by the browser. |
| FID is reported. |
fid.loading_state MUST be one of the following:
| Value | Description |
|---|---|
| The document and all sub-resources have finished loading. |
| The document has been parsed and deferred scripts have finished loading but other sub-resources such as async scripts, images, stylesheets, and frames are still loading. |
| The document has finished loading and the document has been parsed but sub-resources such as scripts, images, stylesheets, and frames are still loading. |
| The document is still loading. |
The Interaction to Next Paint (INP) attributes contain additional information about the captured web_vitals.interaction_to_next_paint.
| Attribute | Type | Description | Examples |
|---|---|---|---|
| string | experimentalThe status information for INP. |
|
| long | experimentalThe number of INP updates during the entire lifespan. |
|
| long | experimentalThe number of interactions, during the entire lifespan, that exceed 40 milliseconds. |
|
| string | experimentalThe document's loading state recorded at the point in time when the INP was captured. |
|
| double | experimentalThe value of the INP object's |
|
| double | experimentalThe value of the INP object's |
|
| string | experimentalThe value of the INP object's |
|
| double | experimentalThe value of the INP object's |
|
| double | experimentalThe value of the INP object's |
|
| double | experimentalHow long it took for the event handler to execute. This is calculated as |
|
| boolean | experimentalThe value of the INP object's |
|
| string[] | experimentalThe element's xpath. Might be missing, for example, for element's that are inside a shadow DOM. |
|
| string | experimentalThe element's tag name. Might be missing, for example, for element's that are inside a shadow DOM. |
|
inp.status MUST be one of the following:
| Value | Description |
|---|---|
| INP is not reported because the value is below the threshold of 40 milliseconds. |
| INP is not reported because capturing of page and view summaries is disabled (only used for activity events). |
| INP is not reported because no relevant user interaction happened. |
| INP is not supported by the browser. |
| INP is reported. |
inp.loading_state MUST be one of the following:
| Value | Description |
|---|---|
| The document and all sub-resources have finished loading. |
| The document has been parsed and deferred scripts have finished loading but other sub-resources such as async scripts, images, stylesheets, and frames are still loading. |
| The document has finished loading and the document has been parsed but sub-resources such as scripts, images, stylesheets, and frames are still loading. |
| The document is still loading. |
The Cumulative Layout Shift (CLS) attributes contain additional information about the captured web_vitals.cumulative_layout_shift.
| Attribute | Type | Description | Examples |
|---|---|---|---|
| string | experimentalThe status information for CLS. |
|
| long | experimentalThe number of CLS updates during the entire lifespan. |
|
| string | experimentalThe document's loading state recorded at the point in time when the CLS was captured. |
|
| double | experimentalThe final CLS value. |
|
| string[] | experimentalThe xpath of the element causing the largest layout shift. Might be missing, for example, for elements that are inside a shadow DOM. |
|
| string | experimentalThe tag name of the element causing the largest layout shift. Might be missing, for example, for elements that are inside a shadow DOM. |
|
| double | experimentalThe time when the largest layout shift occurred. The value is relative to |
|
| double | experimentalThe layout shift score of the element causing the largest layout shift. |
|
cls.status MUST be one of the following:
| Value | Description |
|---|---|
| CLS is not reported because the page was loaded in the background or backgrounded before the browser painted any content. |
| CLS is not reported because capturing of page and view summaries is disabled (only used for activity events). |
| CLS is not supported by the browser. |
| CLS is reported. |
cls.loading_state MUST be one of the following:
| Value | Description |
|---|---|
| The document and all sub-resources have finished loading. |
| The document has been parsed and deferred scripts have finished loading but other sub-resources such as async scripts, images, stylesheets, and frames are still loading. |
| The document has finished loading and the document has been parsed but sub-resources such as scripts, images, stylesheets, and frames are still loading. |
| The document is still loading. |
| Attribute | Type | Description | Examples |
|---|---|---|---|
| string | experimentalThe status information for long task information. |
|
| long | experimentalThe number of all long tasks observed during the entire lifespan. |
|
| long | experimentalThe average duration of all observed long tasks in milliseconds. |
|
| record[] | experimentalThe start time and the duration of the slowest observed long tasks in milliseconds. The start time is relative to the user event's |
|
| long | experimentalThe number of long tasks from the same browser context or frame observed during the entire lifespan. Only long tasks with |
|
| long | experimentalThe average duration of the observed long tasks from the same browser context or frame in milliseconds. Only long tasks with |
|
| record[] | experimentalThe start time and the duration of the slowest observed long tasks from the same browser context or frame in milliseconds. The start time is relative to the user event's |
|
long_task.status MUST be one of the following:
| Value | Description |
|---|---|
| Long task information is not reported because capturing of page and view summaries is disabled (only used for activity events). |
| Long task information is not reported because no long task was observed. |
| Long tasks API is not supported by the browser. |
| Long task information is reported. |