Semantic conventions for long task events in Dynatrace RUM. Long task capturing is an upcoming feature of RUM JavaScript that will be available soon.
This query searches for all long tasks.
fetch user.events| filter characteristics.has_long_task == true
| Attribute | Type | Description | Examples |
|---|---|---|---|
characteristics.classifier | string | experimental Fixed value other. | other |
characteristics.has_long_task | boolean | stable Fixed value true. | true |
| Attribute | Type | Description | Examples |
|---|---|---|---|
long_task.name | string | experimental One of the following strings refers to the browsing context or frame that can be attributed to the long task: cross-origin-ancestor, cross-origin-descendant, cross-origin-unreachable, multiple-contexts, same-origin-ancestor, same-origin-descendant, same-origin, self, unknown. | cross-origin-ancestor |
long_task.attribution.container_id | string | experimental The ID of the container where the long task happened. | app-iframe |
long_task.attribution.container_name | string | experimental The name of the container where the long task happened. | app-iframe |
long_task.attribution.container_src | string | experimental The source of the container where the long task happened. | http://www.dynatrace.com |
long_task.attribution.container_type | string | experimental The type of container where the long task happened. | iframe |
long_task.attribution.name | string | experimental The name of the attribution. | unknown |
Only available for user events sent by RUM JavaScript and in case a user action was active when the CSP event occurred.
| Attribute | Type | Description | Examples |
|---|---|---|---|
user_action.instance_id | uid | experimental The ID of the active user action. The user_action.instance_id is an 8-byte ID and hex-encoded if shown as a string. | f76281848bd8288c |