From 8407cb292dd413dc975d68dc9ec686c2f1de8bb7 Mon Sep 17 00:00:00 2001 From: Rosa Trieu Date: Fri, 11 Jul 2025 12:00:10 -0700 Subject: [PATCH 1/4] Clean up inaccurate mentions of metrics --- content/en/real_user_monitoring/_index.md | 2 +- .../browser/data_collected.md | 30 +++++++++---------- .../browser/frustration_signals.md | 2 +- .../browser/monitoring_page_performance.md | 22 +++++++------- .../monitoring_resource_performance.md | 4 +-- .../browser/optimizing_performance/_index.md | 6 ++-- .../browser/tracking_user_actions.md | 4 +-- .../explorer/watchdog_insights.md | 4 +-- .../guide/compute-apdex-with-rum-data.md | 2 +- .../android/data_collected.md | 26 ++++++++-------- .../flutter/data_collected.md | 6 ++-- .../ios/data_collected.md | 22 +++++++------- .../kotlin_multiplatform/data_collected.md | 6 ++-- .../mobile_vitals/_index.md | 4 +-- .../react_native/data_collected.md | 6 ++-- .../roku/data_collected.md | 26 ++++++++-------- .../unity/data_collected.md | 6 ++-- .../platform/dashboards/performance.md | 4 +-- .../dashboards/testing_and_deployment.md | 8 ++--- .../platform/generate_metrics.md | 4 +-- 20 files changed, 97 insertions(+), 97 deletions(-) diff --git a/content/en/real_user_monitoring/_index.md b/content/en/real_user_monitoring/_index.md index 0227b302c409a..6b7ab29011a8b 100644 --- a/content/en/real_user_monitoring/_index.md +++ b/content/en/real_user_monitoring/_index.md @@ -141,7 +141,7 @@ Select an application from the top navigation, or follow the setup instructions The [RUM Performance Monitoring summary][1] page provides relevant and actionable insights for both web and mobile applications. You have a tailored experience for each platform that helps you: -- **Focus on key data points** by platform, such as the UI latency for web or mobile crashes +- **Focus on key datapoints** by platform, such as the UI latency for web or mobile crashes - **Monitor application health** through familiar KPIs, such as Core Web Vitals for web apps or hang rate for iOS, to assess app reliability - **Dive into investigations directly** from interactive widgets without leaving the page diff --git a/content/en/real_user_monitoring/browser/data_collected.md b/content/en/real_user_monitoring/browser/data_collected.md index da7778648a692..d7cab07466f4e 100644 --- a/content/en/real_user_monitoring/browser/data_collected.md +++ b/content/en/real_user_monitoring/browser/data_collected.md @@ -27,9 +27,9 @@ further_reading: ## Overview -The RUM Browser SDK generates events that have associated metrics and attributes. Every RUM event has all of the [default attributes](#default-attributes), for example, the URL of the page (`view.url`) and user information such as their device type (`device.type`) and their country (`geo.country`). +The RUM Browser SDK generates events that have associated telemetry and attributes. Every RUM event has all of the [default attributes](#default-attributes), for example, the URL of the page (`view.url`) and user information such as their device type (`device.type`) and their country (`geo.country`). -There are additional [metrics and attributes specific to a given event type](#event-specific-metrics-and-attributes). For example, the `view.loading_time` metric is associated with view events, and the `resource.method` attribute is associated with resource events. +There are additional [telemetry and attributes specific to a given event type](#event-specific-telemetry-and-attributes). For example, the `view.loading_time` telemetry is associated with view events, and the `resource.method` attribute is associated with resource events. | Event Type | Retention | Description | |----------------|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| @@ -48,11 +48,11 @@ The following diagram illustrates the RUM event hierarchy: See a complete list of [Standard Attributes][1] for RUM Browser. By default, the attributes are attached to each event type, so you can use them regardless of the RUM event type being queried. -## Event-specific metrics and attributes +## Event-specific telemetry and attributes -### Session metrics +### Session KPIs -| Metric | Type | Description | +| KPI | Type | Description | |------------|--------|----------------------------| | `session.time_spent` | number (ns) | Duration of the user session. | | `session.view.count` | number | Count of all views collected for this session. | @@ -83,9 +83,9 @@ See a complete list of [Standard Attributes][1] for RUM Browser. By default, the | `session.last_view.url_query` | object | The query string parts of the URL decomposed as query params key/value attributes. | | `session.last_view.url_scheme` | object | The scheme part of the URL. | -### View timing metrics +### View timing telemetry -**Note**: View timing metrics include time that a page is open in the background. +**Note**: View timing telemetry includes time that a page is open in the background. | Attribute | Type | Description | |---------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| @@ -110,16 +110,16 @@ See a complete list of [Standard Attributes][1] for RUM Browser. By default, the | `view.resource.count` | number | Count of all resources collected for this view. | | `view.action.count` | number | Count of all actions collected for this view. | -### Resource timing metrics +### Resource timing telemetry Detailed network timing data for the loading of an application's resources are collected with the [Performance Resource Timing API][10]. -| Metric | Type | Description | +| Telemetry | Type | Description | |----------------------------------------|----------------|-------------------------------------------------------------------------------------------------------------------------------------------| | `resource.duration` | number | Entire time spent loading the resource. | | `resource.size` | number (bytes) | Resource size. | | `resource.connect.duration` | number (ns) | Time spent establishing a connection to the server (connectEnd - connectStart). | -| `resource.ssl.duration` | number (ns) | Time spent for the TLS handshake. If the last request is not over HTTPS, this metric does not appear (connectEnd - secureConnectionStart). | +| `resource.ssl.duration` | number (ns) | Time spent for the TLS handshake. If the last request is not over HTTPS, this telemetry does not appear (connectEnd - secureConnectionStart). | | `resource.dns.duration` | number (ns) | Time spent resolving the DNS name of the last request (domainLookupEnd - domainLookupStart). | | `resource.redirect.duration` | number (ns) | Time spent on subsequent HTTP requests (redirectEnd - redirectStart). | | `resource.first_byte.duration` | number (ns) | Time spent waiting for the first byte of response to be received (responseStart - RequestStart). | @@ -141,9 +141,9 @@ Detailed network timing data for the loading of an application's resources are c | `resource.provider.domain` | string | The resource provider domain. | | `resource.provider.type` | string | The resource provider type (for example, `first-party`, `cdn`, `ad`, or `analytics`). | -### Long task timing metrics +### Long task timing telemetry -| Metric | Type | Description | +| Telemetry | Type | Description | |------------|--------|----------------------------| | `long_task.duration` | number | Duration of the long task. | @@ -164,9 +164,9 @@ Source errors include code-level information about the error. For more informati |-----------------|--------|-------------------------------------------------------------------| | `error.type` | string | The error type (or error code in some cases). | -### Action timing metrics +### Action timing telemetry -| Metric | Type | Description | +| Telemetry | Type | Description | |--------------|--------|--------------------------| | `action.loading_time` | number (ns) | The loading time of the action. See how it is calculated in the [Tracking User Actions documentation][13]. | | `action.long_task.count` | number | Count of all long tasks collected for this action. | @@ -218,5 +218,5 @@ Source errors include code-level information about the error. For more informati [10]: https://developer.mozilla.org/en-US/docs/Web/API/PerformanceResourceTiming [11]: /real_user_monitoring/browser/collecting_browser_errors#error-sources [12]: https://developer.mozilla.org/en-US/docs/Web/API/PerformanceResourceTiming -[13]: /real_user_monitoring/browser/tracking_user_actions/?tab=npm#action-timing-metrics +[13]: /real_user_monitoring/browser/tracking_user_actions/?tab=npm#action-timing-telemetry [14]: /real_user_monitoring/browser/tracking_user_actions/?tab=npm#custom-actions diff --git a/content/en/real_user_monitoring/browser/frustration_signals.md b/content/en/real_user_monitoring/browser/frustration_signals.md index f966f1694459b..a2e905484de60 100644 --- a/content/en/real_user_monitoring/browser/frustration_signals.md +++ b/content/en/real_user_monitoring/browser/frustration_signals.md @@ -65,7 +65,7 @@ Frustration signals require actions. Enabling `trackFrustrations` automatically ## Usage -Frustration signals appear as high-level data points representing sources of user frustration on the [**RUM Applications** page][1]. To display a list of frustration counts in the [RUM Explorer][2], click the **Options** button and add a column for `@session.frustration.count`. +Frustration signals appear as high-level datapoints representing sources of user frustration on the [**RUM Applications** page][1]. To display a list of frustration counts in the [RUM Explorer][2], click the **Options** button and add a column for `@session.frustration.count`. ### Application list diff --git a/content/en/real_user_monitoring/browser/monitoring_page_performance.md b/content/en/real_user_monitoring/browser/monitoring_page_performance.md index 43fa3f93baf0a..d3c801c2ffa37 100644 --- a/content/en/real_user_monitoring/browser/monitoring_page_performance.md +++ b/content/en/real_user_monitoring/browser/monitoring_page_performance.md @@ -23,29 +23,29 @@ further_reading: ## Overview -RUM view events collect extensive performance metrics for every pageview. Monitor your application's pageviews and explore performance metrics in dashboards and the RUM Explorer. +RUM view events collect extensive performance telemetry for every pageview. Monitor your application's pageviews and explore performance telemetry in dashboards and the RUM Explorer. {{< img src="real_user_monitoring/browser/waterfall-4.png" alt="A waterfall graph on the Performance tab of a RUM view in the RUM Explorer" style="width:100%;" >}} -You can access performance metrics for your views in: +You can access performance telemetry for your views in: -- Out-of-the-box [RUM dashboards][1], which provide a high-level view of your application's performance. For example, you can filter on [default attributes][2] collected by RUM to surface issues impacting a subset of users in the [Performance Overview dashboard][3]. You can also clone this dashboard, customize it to your needs, and use any [RUM performance metrics](#all-performance-metrics) in the dashboard's query. +- Out-of-the-box [RUM dashboards][1], which provide a high-level view of your application's performance. For example, you can filter on [default attributes][2] collected by RUM to surface issues impacting a subset of users in the [Performance Overview dashboard][3]. You can also clone this dashboard, customize it to your needs, and use any [RUM performance telemetry](#all-performance-telemetry) in the dashboard's query. - A performance waterfall, accessible for every RUM view event in the [RUM Explorer][4], which enables you to troubleshoot the performance of a specific page view. It displays how your website assets and resources, long tasks, and frontend errors affect the page-level performance for your end users. ## Event timings and core web vitals
- Datadog's Core Web Vitals metrics are available from the @datadog/browser-rum package v2.2.0+. + Datadog's Core Web Vitals telemetry is available from the @datadog/browser-rum package v2.2.0+.
-[Google's Core Web Vitals][5] are a set of three metrics designed to monitor a site's user experience. These metrics focus on giving you a view of load performance, interactivity, and visual stability. Each metric comes with guidance on the range of values that translate to good user experience. Datadog recommends monitoring the 75th percentile for these metrics. +[Google's Core Web Vitals][5] are a set of three KPIs designed to monitor a site's user experience. These KPIs focus on giving you a view of load performance, interactivity, and visual stability. Each KPI comes with guidance on the range of values that translate to good user experience. Datadog recommends monitoring the 75th percentile for these KPIs. {{< img src="real_user_monitoring/browser/core-web-vitals-1.png" alt="Core Web Vitals summary visualization" >}} - Interaction to Next Paint and Largest Contentful Paint are not collected for pages opened in the background (for example, in a new tab or a window without focus). -- Metrics collected from your real users' pageviews may differ from those calculated for pages loaded in a fixed, controlled environment such as a [Synthetic browser test][6]. Synthetic Monitoring displays Largest Contentful Paint and Cumulative Layout Shift as lab metrics, not real metrics. +- Telemetry collected from your real users' pageviews may differ from those calculated for pages loaded in a fixed, controlled environment such as a [Synthetic browser test][6]. Synthetic Monitoring displays Largest Contentful Paint and Cumulative Layout Shift as lab telemetry, not real telemetry. -| Metric | Focus | Description | Target value | +| Datapoint | Focus | Description | Target value | |--------------------------|------------------|-------------------------------------------------------------------------------------------------------|--------------| | [Largest Contentful Paint][7] | Load performance | Moment in the page load timeline in which the largest DOM object in the viewport (as in, visible on screen) is rendered. | <2.5s | | [Interaction To Next Paint][19]| Interactivity | Longest duration between a user's interaction with the page and the next paint. Requires RUM SDK v5.1.0. | <200ms | @@ -53,7 +53,7 @@ You can access performance metrics for your views in: ### Core web vitals target elements -Identifying what element triggered a high Core Web Vitals metric is the first step in understanding the root cause and being able to improve performance. +Identifying what element triggered a high Core Web Vitals KPI is the first step in understanding the root cause and being able to improve performance. RUM reports the element that is associated with each Core Web Vital instance: - For Largest Contentful Paint, RUM reports the CSS Selector of the element corresponding to the largest contentful paint. @@ -61,7 +61,7 @@ RUM reports the element that is associated with each Core Web Vital instance: - For First Input Delay, RUM reports the CSS selector of the first element the user interacted with. - For Cumulative Layout Shift, RUM reports the CSS selector of the most shifted element contributing to the CLS. -## All performance metrics +## All performance telemetry | Attribute | Type | Description | |---------------------------------|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| @@ -90,7 +90,7 @@ RUM reports the element that is associated with each Core Web Vital instance: For single page applications (SPAs), the RUM Browser SDK differentiates between `initial_load` and `route_change` navigation with the `loading_type` attribute. If an interaction on your web page leads to a different URL without a full refresh of the page, the RUM SDK starts a new view event with `loading_type:route_change`. RUM tracks URL changes using the [History API][16]. -Datadog provides a unique performance metric, `loading_time`, which calculates the time needed for a page to load. This metric works for both `initial_load` and `route_change` navigation. +Datadog provides a unique performance KPI, `loading_time`, which calculates the time needed for a page to load. This KPI works for both `initial_load` and `route_change` navigation. ### How loading time is calculated @@ -144,7 +144,7 @@ window.DD_RUM.init({ The RUM SDK automatically monitors frameworks that rely on hash (`#`) navigation. The SDK watches for `HashChangeEvent` and issues a new view. Events coming from an HTML anchor tag which do not affect the current view context are ignored. -## Create custom performance metrics +## Create custom performance telemetry ### Measure component-level performance with custom vitals diff --git a/content/en/real_user_monitoring/browser/monitoring_resource_performance.md b/content/en/real_user_monitoring/browser/monitoring_resource_performance.md index af5eab47082c6..2788df2a8d4e7 100644 --- a/content/en/real_user_monitoring/browser/monitoring_resource_performance.md +++ b/content/en/real_user_monitoring/browser/monitoring_resource_performance.md @@ -31,7 +31,7 @@ See [Connect RUM and Traces][2] for information about setting up this feature. {{< img src="real_user_monitoring/browser/resource_performance_graph.png" alt="APM Trace information for a RUM Resource" >}} -## Resource timing and metrics +## Resource timing and telemetry Detailed network timing data for resources is collected from the Fetch and XHR native browser methods and from the [Performance Resource Timing API][3]. @@ -40,7 +40,7 @@ Detailed network timing data for resources is collected from the Fetch and XHR n | `resource.duration` | number | Entire time spent loading the resource. | | `resource.size` | number (bytes) | Resource size. | | `resource.connect.duration` | number (ns) | Time spent establishing a connection to the server (connectEnd - connectStart). | -| `resource.ssl.duration` | number (ns) | Time spent for the TLS handshake. If the last request is not over HTTPS, this metric does not appear (connectEnd - secureConnectionStart). | +| `resource.ssl.duration` | number (ns) | Time spent for the TLS handshake. If the last request is not over HTTPS, this telemetry does not appear (connectEnd - secureConnectionStart). | | `resource.dns.duration` | number (ns) | Time spent resolving the DNS name of the last request (domainLookupEnd - domainLookupStart). | | `resource.redirect.duration` | number (ns) | Time spent on subsequent HTTP requests (redirectEnd - redirectStart). | | `resource.first_byte.duration` | number (ns) | Time spent waiting for the first byte of response to be received (responseStart - RequestStart). | diff --git a/content/en/real_user_monitoring/browser/optimizing_performance/_index.md b/content/en/real_user_monitoring/browser/optimizing_performance/_index.md index 586ee8b5b5d5d..01ee207df2b62 100644 --- a/content/en/real_user_monitoring/browser/optimizing_performance/_index.md +++ b/content/en/real_user_monitoring/browser/optimizing_performance/_index.md @@ -21,7 +21,7 @@ further_reading: {{< img src="real_user_monitoring/browser/optimizing_performance/optimization-workflow.mp4" alt="RUM Performance Optimization helps you find the root cause of browser performance issues based on real user traffic." video="true" >}} -The Optimization page helps to identify the root cause of browser performance issues using real user traffic data. Troubleshoot the causes of slow pages using browser metrics such as [Core Web Vitals][1] (CWV) and Datadog's custom [Loading Time][2] metric, which evaluates full-page load time from the user's perspective. +The Optimization page helps to identify the root cause of browser performance issues using real user traffic data. Troubleshoot the causes of slow pages using browser KPIs such as [Core Web Vitals][1] (CWV) and Datadog's custom [Loading Time][2] KPI, which evaluates full-page load time from the user's perspective. For deeper analysis, the Optimization page provides granular breakdowns of Core Web Vitals by user demographics such as browser, region, and app version. You can use this information to track performance trends over time, understand which user groups are most affected, and prioritize optimizations with precision. @@ -45,10 +45,10 @@ From this view, there are two ways to select a page or vital: Available vitals include: -- **[Loading Time (LT)][2]**: Datadog's custom metric that measures the time for a page to load from a user's perspective. +- **[Loading Time (LT)][2]**: Datadog's custom KPI that measures the time for a page to load from a user's perspective. - **[Largest Contentful Paint (LCP)][8]**: Measures how quickly the largest visual element on your page loads, which is a critical factor in both user experience and SEO rankings. A slow LCP can frustrate users, increase bounce rates, and hurt search visibility. - **[First Contentful Paint (FCP)][9]**: Measures the time from when the user first navigated to the page to when any part of the page's content is rendered on the screen. A fast FCP helps reassure the user that something is happening. -- **[Cumulative Layout Shift (CLS)][10]**: Measures the largest burst of unexpected layout shifts that occur during a page's life cycle. A layout shift happens when a visible element moves from one rendered frame to the next without any user interaction, disrupting the visual stability of the page. An important metric for measuring visual stability because it helps quantify how often users experience unexpected layout shifts. A low CLS helps ensure that the page is delightful. +- **[Cumulative Layout Shift (CLS)][10]**: Measures the largest burst of unexpected layout shifts that occur during a page's life cycle. A layout shift happens when a visible element moves from one rendered frame to the next without any user interaction, disrupting the visual stability of the page. An important KPI for measuring visual stability because it helps quantify how often users experience unexpected layout shifts. A low CLS helps ensure that the page is delightful. - **[Interaction to Next Paint (INP)][11]**: Measures how long it takes for a page to visually respond after a user interacts with the page. ## Filter and evaluate diff --git a/content/en/real_user_monitoring/browser/tracking_user_actions.md b/content/en/real_user_monitoring/browser/tracking_user_actions.md index 92f4253d06175..646f5cc5b647d 100644 --- a/content/en/real_user_monitoring/browser/tracking_user_actions.md +++ b/content/en/real_user_monitoring/browser/tracking_user_actions.md @@ -37,11 +37,11 @@ To control which information is sent to Datadog, you can [mask action names with The RUM Browser SDK automatically tracks clicks to generate click actions. A one-click action generally represents one user click, except when the same element is clicked multiple times in a row, which is considered a single action (see [Frustration Signals "rage clicks"][7]). -## Action timing metrics +## Action timing telemetry For information about the default attributes for all RUM event types, see [RUM Browser Data Collected][3]. -| Metric | Type | Description | +| Telemetry | Type | Description | |--------------|--------|--------------------------| | `action.loading_time` | number (ns) | The loading time of the action. | | `action.long_task.count` | number | Count of all long tasks collected for this action. | diff --git a/content/en/real_user_monitoring/explorer/watchdog_insights.md b/content/en/real_user_monitoring/explorer/watchdog_insights.md index 6b17ae8898fc9..609fbfe5287a4 100644 --- a/content/en/real_user_monitoring/explorer/watchdog_insights.md +++ b/content/en/real_user_monitoring/explorer/watchdog_insights.md @@ -59,9 +59,9 @@ Latency outliers are computed for [Core Web Vitals][4] such as First Contentful In the **banner card** view, you can see: * The field name -* The performance metric value containing the field and the baseline for the rest of the data +* The performance telemetry value containing the field and the baseline for the rest of the data -In the **full side panel**, you can see a timeseries graph about the performance metric with an X axis of increments of `p50`, `p75`, `p99`, and `max`, along with a list of RUM events that contain the field. +In the **full side panel**, you can see a timeseries graph about the performance telemetry with an X axis of increments of `p50`, `p75`, `p99`, and `max`, along with a list of RUM events that contain the field. {{< img src="real_user_monitoring/explorer/watchdog_insights/latency_outlier_side_panel-1.png" alt="Latency Outlier full side panel view" style="width:100%;" >}} diff --git a/content/en/real_user_monitoring/guide/compute-apdex-with-rum-data.md b/content/en/real_user_monitoring/guide/compute-apdex-with-rum-data.md index beccd7c74b36b..4f26744a8df74 100644 --- a/content/en/real_user_monitoring/guide/compute-apdex-with-rum-data.md +++ b/content/en/real_user_monitoring/guide/compute-apdex-with-rum-data.md @@ -148,7 +148,7 @@ You can also calculate other Apdex scores with the following methods: - To compute the Apdex score for a specific application, add an additional `@application.name` query and update your formula. - To compute the Apdex score with another RUM performance metric such as First Contentful Paint, replace `@view.LargestContentfulPaint` with `@view.FirstContentfulPaint` in the queries. -To compute additional performance indicators for your applications, determine what data points you need and which RUM events are relevant for you before [creating a quick graph](#create-a-quick-graph). +To compute additional performance indicators for your applications, determine what datapoints you need and which RUM events are relevant for you before [creating a quick graph](#create-a-quick-graph). ## Further Reading diff --git a/content/en/real_user_monitoring/mobile_and_tv_monitoring/android/data_collected.md b/content/en/real_user_monitoring/mobile_and_tv_monitoring/android/data_collected.md index 5c563d20733df..e9f7408296c19 100644 --- a/content/en/real_user_monitoring/mobile_and_tv_monitoring/android/data_collected.md +++ b/content/en/real_user_monitoring/mobile_and_tv_monitoring/android/data_collected.md @@ -14,11 +14,11 @@ further_reading: ## Overview -The RUM Android SDK generates events that have associated metrics and attributes. Metrics are quantifiable values that can be used for measurements related to the event. Attributes are non-quantifiable values used to slice metrics data (group by) in analytics. +The RUM Android SDK generates events that have associated telemetry and attributes. Telemetry are quantifiable values that can be used for measurements related to the event. Attributes are non-quantifiable values used to slice telemetry values (group by) in analytics. Every RUM event has all of the [default attributes](#default-attributes), for example, the device type (`device.type`) and user information such as their name (`usr.name`) and their country (`geo.country`). -There are additional [metrics and attributes that are specific to a given event type](#event-specific-metrics-and-attributes). For example, the metric `view.time_spent` is associated with "view" events and the attribute `resource.method` is associated with "resource" events. +There are additional [telemetry and attributes that are specific to a given event type](#event-specific-telemetry-and-attributes). For example, the telemetry `view.time_spent` is associated with "view" events and the attribute `resource.method` is associated with "resource" events. | Event Type | Retention | Description | |----------------|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| @@ -128,13 +128,13 @@ You can enable [tracking user info][10] globally to collect and apply user attri | `usr.email` | string | Email of the user. | -## Event-specific metrics and attributes +## Event-specific telemetry and attributes -Metrics are quantifiable values that can be used for measurements related to the event. Attributes are non-quantifiable values used to slice metrics data (group by) in analytics. +Telemetry are quantifiable values that can be used for measurements related to the event. Attributes are non-quantifiable values used to slice telemetry values (group by) in analytics. -### Session metrics +### Session KPIs -| Metric | Type | Description | +| KPI | Type | Description | |------------|--------|----------------------------| | `session.time_spent` | number (ns) | Time spent on a session. | | `session.view.count` | number | Count of all views collected for this session. | @@ -158,11 +158,11 @@ Metrics are quantifiable values that can be used for measurements related to the | `session.useragent` | string | System user agent info to interpret device info. | | `session.has_replay` | boolean | Indicates if the session has a captured Session Replay recording attached to visually play the user experience. | -### View metrics +### View telemetry RUM action, error, resource, and long task events contain information about the active RUM view event at the time of collection. -| Metric | Type | Description | +| Telemetry | Type | Description | |----------------------------------------|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | `view.time_spent` | number (ns) | Time spent on this view. | | `view.long_task.count` | number | Count of all long tasks collected for this view. | @@ -182,15 +182,15 @@ RUM action, error, resource, and long task events contain information about the | `view.url` | string | Canonical name of the class corresponding to the event. | | `view.name` | string | Customizable name of the view corresponding to the event. | -### Resource metrics +### Resource telemetry -| Metric | Type | Description | +| Telemetry | Type | Description | |----------------------------------------|----------------|-------------------------------------------------------------------------------------------------------------------------------------------| | `resource.duration` | number (ns) | Entire time spent loading the resource. | | `resource.size` | number (bytes) | Resource size. | | `resource.connect.duration` | number (ns) | Time spent establishing a connection to the server (connectEnd - connectStart). | -| `resource.ssl.duration` | number (ns) | Time spent for the TLS handshake. If the last request is not over HTTPS, this metric does not appear (connectEnd - secureConnectionStart). | +| `resource.ssl.duration` | number (ns) | Time spent for the TLS handshake. If the last request is not over HTTPS, this telemetry does not appear (connectEnd - secureConnectionStart). | | `resource.dns.duration` | number (ns) | Time spent resolving the DNS name of the last request (domainLookupEnd - domainLookupStart). | | `resource.redirect.duration` | number (ns) | Time spent on subsequent HTTP requests (redirectEnd - redirectStart). | | `resource.first_byte.duration` | number (ns) | Time spent waiting for the first byte of response to be received (responseStart - RequestStart). | @@ -237,9 +237,9 @@ Network errors include information about failing HTTP requests. The following fa | `error.resource.provider.domain` | string | The resource provider domain. | | `error.resource.provider.type` | string | The resource provider type (for example, `first-party`, `cdn`, `ad`, or `analytics`). | -### Action timing metrics +### Action timing telemetry -| Metric | Type | Description | +| Telemetry | Type | Description | |--------------|--------|--------------------------| | `action.loading_time` | number (ns) | The loading time of the action. | | `action.long_task.count` | number | Count of all long tasks collected for this action. | diff --git a/content/en/real_user_monitoring/mobile_and_tv_monitoring/flutter/data_collected.md b/content/en/real_user_monitoring/mobile_and_tv_monitoring/flutter/data_collected.md index 12b55f212c108..d76a749b6af81 100644 --- a/content/en/real_user_monitoring/mobile_and_tv_monitoring/flutter/data_collected.md +++ b/content/en/real_user_monitoring/mobile_and_tv_monitoring/flutter/data_collected.md @@ -15,12 +15,12 @@ further_reading: --- ## Overview -The Datadog Flutter SDK for RUM generates events with associated metrics and attributes. Metrics are quantifiable values that can be used for measurements related to the event. Attributes are non-quantifiable values used to slice metrics data (group by) in the RUM Explorer. +The Datadog Flutter SDK for RUM generates events with associated telemetry and attributes. Telemetry are quantifiable values that can be used for measurements related to the event. Attributes are non-quantifiable values used to slice telemetry values (group by) in the RUM Explorer. Most Flutter Monitoring data is collected by native Datadog iOS and Android SDKs for RUM, and is retained for the same periods of time. -* For iOS event-specific metrics and attributes, see [RUM iOS Data Collected][1]. -* For Android event-specific metrics and attributes, see [RUM Android Data Collected][2]. +* For iOS event-specific telemetry and attributes, see [RUM iOS Data Collected][1]. +* For Android event-specific telemetry and attributes, see [RUM Android Data Collected][2]. ## Further reading diff --git a/content/en/real_user_monitoring/mobile_and_tv_monitoring/ios/data_collected.md b/content/en/real_user_monitoring/mobile_and_tv_monitoring/ios/data_collected.md index bcb4a85217726..e94dac59da7b4 100644 --- a/content/en/real_user_monitoring/mobile_and_tv_monitoring/ios/data_collected.md +++ b/content/en/real_user_monitoring/mobile_and_tv_monitoring/ios/data_collected.md @@ -14,11 +14,11 @@ further_reading: ## Overview -The RUM iOS SDK generates events that have associated metrics and attributes. Metrics are quantifiable values that can be used for measurements related to the event. Attributes are non-quantifiable values used to slice metrics data (group by) in analytics. +The RUM iOS SDK generates events that have associated telemetry and attributes. Telemetry are quantifiable values that can be used for measurements related to the event. Attributes are non-quantifiable values used to slice telemetry values (group by) in analytics. Every RUM event has all of the [default attributes](#default-attributes), for example, the device type (`device.type`) and user information such as their name (`usr.name`) and their country (`geo.country`). -There are additional [metrics and attributes that are specific to a given event type](#event-specific-metrics-and-attributes). For example, the metric `view.time_spent` is associated with "view" events and the attribute `resource.method` is associated with "resource" events. +There are additional [telemetry and attributes that are specific to a given event type](#event-specific-telemetry-and-attributes). For example, the telemetry `view.time_spent` is associated with "view" events and the attribute `resource.method` is associated with "resource" events. | Event Type | Retention | Description | |------------|-----------|-------------------------------------| @@ -131,11 +131,11 @@ You can enable [tracking user info][7] globally to collect and apply user attrib | `usr.email` | string | Email of the user. | -## Event-specific metrics and attributes +## Event-specific telemetry and attributes -### Session metrics +### Session KPIs -| Metric | Type | Description | +| KPI | Type | Description | |---------------------------|-------------|-----------------------------------------------------| | `session.time_spent` | number (ns) | Time spent on a session. | | `session.view.count` | number | Count of all views collected for this session. | @@ -161,11 +161,11 @@ You can enable [tracking user info][7] globally to collect and apply user attrib | `session.useragent` | string | System user agent info to interpret device info. | -### View metrics +### View telemetry RUM action, error, resource, and long task events contain information about the active RUM view event at the time of collection. -| Metric | Type | Description | +| Telemetry | Type | Description | |-----------------------|-------------|------------------------------------------------------------------------------| | `view.time_spent` | number (ns) | Time spent on this view. | | `view.long_task.count` | number | Count of all long tasks collected for this view. | @@ -185,9 +185,9 @@ RUM action, error, resource, and long task events contain information about the | `view.network_settled_time` | number (ns) | Time it took for a view to be fully initiated at the start of the view. | | `view.interaction_to_next_view_time` | number (ns) | Time between the last user interaction in the previous view and start of this (current) view. | -### Resource metrics +### Resource telemetry -| Metric | Type | Description | +| Telemetry | Type | Description | |--------------------------------|----------------|-------------------------------------------------------------------------------------------------| | `resource.duration` | number | Entire time spent loading the resource. | | `resource.size` | number (bytes) | Resource size. | @@ -242,9 +242,9 @@ Network errors include information about failing HTTP requests. The following fa | `error.resource.provider.type` | string | The resource provider type (for example, `first-party`, `cdn`, `ad`, or `analytics`). | -### Action metrics +### Action telemetry -| Metric | Type | Description | +| Telemetry | Type | Description | |-------------------------|-------------|-----------------------------------------------| | `action.loading_time` | number (ns) | The loading time of the action. | | `action.long_task.count` | number | Count of all long tasks collected for this action. | diff --git a/content/en/real_user_monitoring/mobile_and_tv_monitoring/kotlin_multiplatform/data_collected.md b/content/en/real_user_monitoring/mobile_and_tv_monitoring/kotlin_multiplatform/data_collected.md index d6a443263c9f7..2dd6a80215d90 100644 --- a/content/en/real_user_monitoring/mobile_and_tv_monitoring/kotlin_multiplatform/data_collected.md +++ b/content/en/real_user_monitoring/mobile_and_tv_monitoring/kotlin_multiplatform/data_collected.md @@ -16,12 +16,12 @@ further_reading: --- ## Overview -The Datadog Kotlin Multiplatform SDK for RUM generates events with associated metrics and attributes. Metrics are quantifiable values that can be used for measurements related to the event. Attributes are non-quantifiable values used to slice metrics data (group by) in the RUM Explorer. +The Datadog Kotlin Multiplatform SDK for RUM generates events with associated telemetry and attributes. Telemetry are quantifiable values that can be used for measurements related to the event. Attributes are non-quantifiable values used to slice telemetry values (group by) in the RUM Explorer. Most Kotlin Multiplatform Monitoring data is collected by native Datadog iOS and Android SDKs for RUM, and is retained for the same periods of time. -* For iOS event-specific metrics and attributes, see [RUM iOS Data Collected][1]. -* For Android event-specific metrics and attributes, see [RUM Android Data Collected][2]. +* For iOS event-specific telemetry and attributes, see [RUM iOS Data Collected][1]. +* For Android event-specific telemetry and attributes, see [RUM Android Data Collected][2]. ## Further reading diff --git a/content/en/real_user_monitoring/mobile_and_tv_monitoring/mobile_vitals/_index.md b/content/en/real_user_monitoring/mobile_and_tv_monitoring/mobile_vitals/_index.md index d06cb80e55d72..611ddab1de7a2 100644 --- a/content/en/real_user_monitoring/mobile_and_tv_monitoring/mobile_vitals/_index.md +++ b/content/en/real_user_monitoring/mobile_and_tv_monitoring/mobile_vitals/_index.md @@ -25,7 +25,7 @@ further_reading: ## Overview -Real User Monitoring offers Mobile Vitals, which includes a set of data points inspired by frameworks such as [Android Vitals][1] and [Apple's MetricKit][2], which can help compute insights about your mobile application's responsiveness, stability, and resource consumption. Mobile Vitals range from poor, moderate, to good. +Real User Monitoring offers Mobile Vitals, which includes a set of datapoints inspired by frameworks such as [Android Vitals][1] and [Apple's MetricKit][2], which can help compute insights about your mobile application's responsiveness, stability, and resource consumption. Mobile Vitals range from poor, moderate, to good. You can view Mobile Vitals for your application by navigating to **Digital Experience > Performance Summary** and selecting your application. @@ -35,7 +35,7 @@ To access the RUM mobile app performance dashboard, switch to the **Performance* {{< img src="real_user_monitoring/android/android-perf-dash-link.png" alt="Access the mobile performance dashboard from the Performance tab" style="width:90%;">}} -Understand your application's overall health and performance with the line graphs displaying data points across various application versions. To filter on application version or see specific sessions and views, click on a graph. +Understand your application's overall health and performance with the line graphs displaying datapoints across various application versions. To filter on application version or see specific sessions and views, click on a graph. {{< img src="real_user_monitoring/android/android_mobile_vitals_3.png" alt="Event Timings and Mobile Vitals in the RUM Explorer" style="width:90%;">}} diff --git a/content/en/real_user_monitoring/mobile_and_tv_monitoring/react_native/data_collected.md b/content/en/real_user_monitoring/mobile_and_tv_monitoring/react_native/data_collected.md index 015d6ac769ff7..db51d28c658f1 100644 --- a/content/en/real_user_monitoring/mobile_and_tv_monitoring/react_native/data_collected.md +++ b/content/en/real_user_monitoring/mobile_and_tv_monitoring/react_native/data_collected.md @@ -18,12 +18,12 @@ further_reading: --- ## Overview -The Datadog React Native SDK for RUM generates events with associated metrics and attributes. Metrics are quantifiable values that can be used for measurements related to the event. Attributes are non-quantifiable values used to slice metrics data (group by) in the RUM Explorer. +The Datadog React Native SDK for RUM generates events with associated telemetry and attributes. Telemetry are quantifiable values that can be used for measurements related to the event. Attributes are non-quantifiable values used to slice telemetry values (group by) in the RUM Explorer. Most React Native Monitoring data is collected by native Datadog iOS and Android SDKs for RUM, and is retained for the same periods of time. -* For iOS event-specific metrics and attributes, see [RUM iOS Data Collected][1]. -* For Android event-specific metrics and attributes, see [RUM Android Data Collected][2]. +* For iOS event-specific telemetry and attributes, see [RUM iOS Data Collected][1]. +* For Android event-specific telemetry and attributes, see [RUM Android Data Collected][2]. ## Further reading diff --git a/content/en/real_user_monitoring/mobile_and_tv_monitoring/roku/data_collected.md b/content/en/real_user_monitoring/mobile_and_tv_monitoring/roku/data_collected.md index c7eec2b260954..b426022055592 100644 --- a/content/en/real_user_monitoring/mobile_and_tv_monitoring/roku/data_collected.md +++ b/content/en/real_user_monitoring/mobile_and_tv_monitoring/roku/data_collected.md @@ -15,11 +15,11 @@ site_support_id: rum_roku ## Overview -The RUM Roku SDK generates events that have associated metrics and attributes. Metrics are quantifiable values that can be used for measurements related to the event. Attributes are non-quantifiable values used to slice metrics data (group by) in analytics. +The RUM Roku SDK generates events that have associated telemetry and attributes. Telemetry are quantifiable values that can be used for measurements related to the event. Attributes are non-quantifiable values used to slice telemetry values (group by) in analytics. Every RUM event has all of the [default attributes](#default-attributes), for example, the device type (`device.type`) and user information such as their name (`usr.name`) and their country (`geo.country`). -There are additional [metrics and attributes that are specific to a given event type](#event-specific-metrics-and-attributes). For example, the metric `view.time_spent` is associated with "view" events and the attribute `resource.method` is associated with "resource" events. +There are additional [telemetry and attributes that are specific to a given event type](#event-specific-telemetry-and-attributes). For example, the telemetry `view.time_spent` is associated with "view" events and the attribute `resource.method` is associated with "resource" events. | Event Type | Retention | Description | | ---------- | --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | @@ -97,13 +97,13 @@ You can enable [tracking user info][5] globally to collect and apply user attrib | `usr.email` | string | Email of the user. | -## Event-specific metrics and attributes +## Event-specific telemetry and attributes -Metrics are quantifiable values that can be used for measurements related to the event. Attributes are non-quantifiable values used to slice metrics data (group by) in analytics. +Telemetry are quantifiable values that can be used for measurements related to the event. Attributes are non-quantifiable values used to slice telemetry values (group by) in analytics. -### Session metrics +### Session KPIs -| Metric | Type | Description | +| KPI | Type | Description | | ------------------------- | ----------- | --------------------------------------------------- | | `session.time_spent` | number (ns) | Time spent on a session. | | `session.view.count` | number | Count of all views collected for this session. | @@ -126,12 +126,12 @@ Metrics are quantifiable values that can be used for measurements related to the | `session.ip` | string | IP address of the session extracted from the TCP connection of the intake. If you want to stop collecting this attribute, change the setting in your [application details][8]. | | `session.useragent` | string | System user agent info to interpret device info. | -### View metrics +### View telemetry RUM action, error, resource, and long task events contain information about the active RUM view event at the time of collection. -| Metric | Type | Description | +| Telemetry | Type | Description | | ---------------------- | ----------- | ---------------------------------------------------------------------------- | | `view.time_spent` | number (ns) | Time spent on this view. | | `view.long_task.count` | number | Count of all long tasks collected for this view. | @@ -148,15 +148,15 @@ RUM action, error, resource, and long task events contain information about the | `view.url` | string | Canonical name of the class corresponding to the event. | | `view.name` | string | Customizable name of the view corresponding to the event. | -### Resource metrics +### Resource telemetry -| Metric | Type | Description | +| Telemetry | Type | Description | | ------------------------------ | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------ | | `resource.duration` | number (ns) | Entire time spent loading the resource. | | `resource.size` | number (bytes) | Resource size. | | `resource.connect.duration` | number (ns) | Time spent establishing a connection to the server (connectEnd - connectStart). | -| `resource.ssl.duration` | number (ns) | Time spent for the TLS handshake. If the last request is not over HTTPS, this metric does not appear (connectEnd - secureConnectionStart). | +| `resource.ssl.duration` | number (ns) | Time spent for the TLS handshake. If the last request is not over HTTPS, this telemetry does not appear (connectEnd - secureConnectionStart). | | `resource.dns.duration` | number (ns) | Time spent resolving the DNS name of the last request (domainLookupEnd - domainLookupStart). | | `resource.redirect.duration` | number (ns) | Time spent on subsequent HTTP requests (redirectEnd - redirectStart). | | `resource.first_byte.duration` | number (ns) | Time spent waiting for the first byte of response to be received (responseStart - RequestStart). | @@ -201,9 +201,9 @@ Network errors include information about failing HTTP requests. The following fa | `error.resource.provider.domain` | string | The resource provider domain. | | `error.resource.provider.type` | string | The resource provider type (for example, `first-party`, `cdn`, `ad`, or `analytics`). | -### Action timing metrics +### Action timing telemetry -| Metric | Type | Description | +| Telemetry | Type | Description | | ------------------------ | ----------- | -------------------------------------------------- | | `action.loading_time` | number (ns) | The loading time of the action. | | `action.long_task.count` | number | Count of all long tasks collected for this action. | diff --git a/content/en/real_user_monitoring/mobile_and_tv_monitoring/unity/data_collected.md b/content/en/real_user_monitoring/mobile_and_tv_monitoring/unity/data_collected.md index dd9cd0231147b..ba13765a06e1d 100644 --- a/content/en/real_user_monitoring/mobile_and_tv_monitoring/unity/data_collected.md +++ b/content/en/real_user_monitoring/mobile_and_tv_monitoring/unity/data_collected.md @@ -15,12 +15,12 @@ further_reading: --- ## Overview -The Datadog Unity SDK for RUM generates events with associated metrics and attributes. Metrics are quantifiable values that can be used for measurements related to the event. Attributes are non-quantifiable values used to slice metrics data (group by) in the RUM Explorer. +The Datadog Unity SDK for RUM generates events with associated telemetry and attributes. Telemetry are quantifiable values that can be used for measurements related to the event. Attributes are non-quantifiable values used to slice KPI values (group by) in the RUM Explorer. Most Unity Monitoring data is collected by native Datadog iOS and Android SDKs for RUM, and is retained for the same periods of time. -* For iOS event-specific metrics and attributes, see [RUM iOS Data Collected][1]. -* For Android event-specific metrics and attributes, see [RUM Android Data Collected][2]. +* For iOS event-specific telemetry and attributes, see [RUM iOS Data Collected][1]. +* For Android event-specific telemetry and attributes, see [RUM Android Data Collected][2]. ## Further reading diff --git a/content/en/real_user_monitoring/platform/dashboards/performance.md b/content/en/real_user_monitoring/platform/dashboards/performance.md index 98553852db8a6..377c9ab7a55d2 100644 --- a/content/en/real_user_monitoring/platform/dashboards/performance.md +++ b/content/en/real_user_monitoring/platform/dashboards/performance.md @@ -20,7 +20,7 @@ further_reading: The web app performance dashboard offers a bird's-eye view of RUM web applications. It shows: - **Core web vitals**: - For all views, three browser performance metrics are highlighted: Largest Contentful Paint, First Input Delay, and Cumulative Layout Shift. Other performance metrics, such as Load Time, are also available. + For all views, three browser performance KPIs are highlighted: Largest Contentful Paint, First Input Delay, and Cumulative Layout Shift. Other performance telemetry, such as Load Time, is also available. - **XHR and Fetch requests and resources**: For all views, identify bottlenecks when your application loads. - **Long tasks** : Events that block the browser's main thread for more than 50ms. @@ -35,7 +35,7 @@ For more information about the data displayed, see [RUM Browser Data Collected][ The mobile app performance dashboard gives an overview of RUM mobile applications. It shows: - **Mobile vitals**: - For all screens, four mobile performance metrics are highlighted: slow renders, CPU ticks per seconds, frozen frames, and memory usage. Other performance metrics, such as crash-free sessions, are also available. + For all screens, four mobile performance KPIs are highlighted: slow renders, CPU ticks per seconds, frozen frames, and memory usage. Other performance telemetry, such as crash-free sessions, is also available. - **Resources analysis**: For all screens, identify bottlenecks when your application requests content. - **Crashes and errors**: diff --git a/content/en/real_user_monitoring/platform/dashboards/testing_and_deployment.md b/content/en/real_user_monitoring/platform/dashboards/testing_and_deployment.md index fdb0fcb1007ae..368d9d4809e15 100644 --- a/content/en/real_user_monitoring/platform/dashboards/testing_and_deployment.md +++ b/content/en/real_user_monitoring/platform/dashboards/testing_and_deployment.md @@ -43,11 +43,11 @@ For more information about the data displayed, see [RUM Browser Data Collected][ The RUM Web App Deployment Tracking dashboard helps you identify when a recent deployment is causing performance issues or new errors within your application. To use this feature, make sure that you [add RUM versions to your application][4]. This dashboard shows: - **Core web vitals**: - For all views, three browser performance metrics are highlighted: Largest Contentful Paint, First Input Delay, and Cumulative Layout Shift. Other performance metrics, such as Load Time, are also available. + For all views, three browser performance KPIs are highlighted: Largest Contentful Paint, First Input Delay, and Cumulative Layout Shift. Other performance telemetry, such as Load Time, is also available. - **Errors**: See a count of errors, percentage of views with errors, and explore ongoing issues. -- **Browser performance metrics**: - Compare performance metrics like loading time, sessions, errors, and load times across different services and versions. +- **Browser performance telemetry**: +Compare performance telemetry like loading time, sessions, errors, and load times across different services and versions. {{< img src="real_user_monitoring/dashboards/dashboard-deployment-web.png" alt="Out-of-the-box web deployment dashboard" style="width:100%" >}} @@ -64,7 +64,7 @@ This dashboard shows: - **Errors**: Review error count by version, error rate by version, and explore ongoing errors. - **Mobile vitals by version**: - For all versions, four mobile performance metrics are highlighted: slow renders, frozen frames, application start time, and memory usage. + For all versions, four mobile performance KPIs are highlighted: slow renders, frozen frames, application start time, and memory usage. {{< img src="real_user_monitoring/dashboards/dashboard-deployment-mobile.png" alt="Out-of-the-box mobile deployment dashboard" style="width:100%" >}} diff --git a/content/en/real_user_monitoring/platform/generate_metrics.md b/content/en/real_user_monitoring/platform/generate_metrics.md index 7c4bdb2d0bda2..7085a7f1ed11e 100644 --- a/content/en/real_user_monitoring/platform/generate_metrics.md +++ b/content/en/real_user_monitoring/platform/generate_metrics.md @@ -64,7 +64,7 @@ To create a custom metric from a search query in the [RUM Explorer][5], click th Your RUM-based custom metric appears in the list below **Custom RUM Metrics**, and there may be a short delay for your metric to become available in [dashboards][9] and [monitors][10]. -Data points are not created for metrics with historical data. Data points for your RUM-based custom metric generate on a ten second interval. Metrics data is retained for 15 months. +Datapoints are not created for metrics with historical data. Datapoints for your RUM-based custom metric generate on a ten second interval. Metrics data is retained for 15 months. ### Add a RUM-based metric on sessions and views @@ -91,7 +91,7 @@ Because you cannot rename an existing metric, Datadog recommends creating anothe ### Delete a RUM-based custom metric -In order to stop the computing of data points from your custom metric and billing, hover over a metric and click the **Delete** icon to the right hand corner. +In order to stop the computing of datapoints from your custom metric and billing, hover over a metric and click the **Delete** icon to the right hand corner. ## Usage From 5c7b61a37b1dea97669f1b221fb0bc55f6554538 Mon Sep 17 00:00:00 2001 From: Rosa Trieu <107086888+rtrieu@users.noreply.github.com> Date: Wed, 16 Jul 2025 10:13:39 -0700 Subject: [PATCH 2/4] Apply suggestions from code review MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Maël Lilensten --- content/en/real_user_monitoring/browser/data_collected.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/real_user_monitoring/browser/data_collected.md b/content/en/real_user_monitoring/browser/data_collected.md index d7cab07466f4e..284e468fa77a2 100644 --- a/content/en/real_user_monitoring/browser/data_collected.md +++ b/content/en/real_user_monitoring/browser/data_collected.md @@ -29,7 +29,7 @@ further_reading: The RUM Browser SDK generates events that have associated telemetry and attributes. Every RUM event has all of the [default attributes](#default-attributes), for example, the URL of the page (`view.url`) and user information such as their device type (`device.type`) and their country (`geo.country`). -There are additional [telemetry and attributes specific to a given event type](#event-specific-telemetry-and-attributes). For example, the `view.loading_time` telemetry is associated with view events, and the `resource.method` attribute is associated with resource events. +There are additional [attributes specific to a given event type](#event-specific-attributes). For example, the `view.loading_time` telemetry is associated with view events, and the `resource.method` attribute is associated with resource events. | Event Type | Retention | Description | |----------------|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| From c48a174b6ec6cd660c2202dcf1c8babb224dea73 Mon Sep 17 00:00:00 2001 From: Rosa Trieu <107086888+rtrieu@users.noreply.github.com> Date: Wed, 16 Jul 2025 10:15:26 -0700 Subject: [PATCH 3/4] Apply suggestions from code review MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Maël Lilensten --- .../browser/data_collected.md | 22 +++++++++---------- .../browser/monitoring_page_performance.md | 2 +- .../monitoring_resource_performance.md | 2 +- .../android/data_collected.md | 4 ++-- .../platform/dashboards/performance.md | 4 ++-- .../dashboards/testing_and_deployment.md | 4 ++-- 6 files changed, 19 insertions(+), 19 deletions(-) diff --git a/content/en/real_user_monitoring/browser/data_collected.md b/content/en/real_user_monitoring/browser/data_collected.md index 284e468fa77a2..a92bb615a8473 100644 --- a/content/en/real_user_monitoring/browser/data_collected.md +++ b/content/en/real_user_monitoring/browser/data_collected.md @@ -48,11 +48,11 @@ The following diagram illustrates the RUM event hierarchy: See a complete list of [Standard Attributes][1] for RUM Browser. By default, the attributes are attached to each event type, so you can use them regardless of the RUM event type being queried. -## Event-specific telemetry and attributes +## Event-specific attributes -### Session KPIs +### Session attributes -| KPI | Type | Description | +| Attribute | Type | Description | |------------|--------|----------------------------| | `session.time_spent` | number (ns) | Duration of the user session. | | `session.view.count` | number | Count of all views collected for this session. | @@ -83,7 +83,7 @@ See a complete list of [Standard Attributes][1] for RUM Browser. By default, the | `session.last_view.url_query` | object | The query string parts of the URL decomposed as query params key/value attributes. | | `session.last_view.url_scheme` | object | The scheme part of the URL. | -### View timing telemetry +### View timing attributes **Note**: View timing telemetry includes time that a page is open in the background. @@ -110,16 +110,16 @@ See a complete list of [Standard Attributes][1] for RUM Browser. By default, the | `view.resource.count` | number | Count of all resources collected for this view. | | `view.action.count` | number | Count of all actions collected for this view. | -### Resource timing telemetry +### Resource timing attributes Detailed network timing data for the loading of an application's resources are collected with the [Performance Resource Timing API][10]. -| Telemetry | Type | Description | +| Attribute | Type | Description | |----------------------------------------|----------------|-------------------------------------------------------------------------------------------------------------------------------------------| | `resource.duration` | number | Entire time spent loading the resource. | | `resource.size` | number (bytes) | Resource size. | | `resource.connect.duration` | number (ns) | Time spent establishing a connection to the server (connectEnd - connectStart). | -| `resource.ssl.duration` | number (ns) | Time spent for the TLS handshake. If the last request is not over HTTPS, this telemetry does not appear (connectEnd - secureConnectionStart). | +| `resource.ssl.duration` | number (ns) | Time spent for the TLS handshake. If the last request is not over HTTPS, this attribute does not appear (connectEnd - secureConnectionStart). | | `resource.dns.duration` | number (ns) | Time spent resolving the DNS name of the last request (domainLookupEnd - domainLookupStart). | | `resource.redirect.duration` | number (ns) | Time spent on subsequent HTTP requests (redirectEnd - redirectStart). | | `resource.first_byte.duration` | number (ns) | Time spent waiting for the first byte of response to be received (responseStart - RequestStart). | @@ -141,9 +141,9 @@ Detailed network timing data for the loading of an application's resources are c | `resource.provider.domain` | string | The resource provider domain. | | `resource.provider.type` | string | The resource provider type (for example, `first-party`, `cdn`, `ad`, or `analytics`). | -### Long task timing telemetry +### Long task timing attributes -| Telemetry | Type | Description | +| Attribute | Type | Description | |------------|--------|----------------------------| | `long_task.duration` | number | Duration of the long task. | @@ -164,9 +164,9 @@ Source errors include code-level information about the error. For more informati |-----------------|--------|-------------------------------------------------------------------| | `error.type` | string | The error type (or error code in some cases). | -### Action timing telemetry +### Action timing attributes -| Telemetry | Type | Description | +| Attribute | Type | Description | |--------------|--------|--------------------------| | `action.loading_time` | number (ns) | The loading time of the action. See how it is calculated in the [Tracking User Actions documentation][13]. | | `action.long_task.count` | number | Count of all long tasks collected for this action. | diff --git a/content/en/real_user_monitoring/browser/monitoring_page_performance.md b/content/en/real_user_monitoring/browser/monitoring_page_performance.md index d3c801c2ffa37..de6b66feb521e 100644 --- a/content/en/real_user_monitoring/browser/monitoring_page_performance.md +++ b/content/en/real_user_monitoring/browser/monitoring_page_performance.md @@ -90,7 +90,7 @@ RUM reports the element that is associated with each Core Web Vital instance: For single page applications (SPAs), the RUM Browser SDK differentiates between `initial_load` and `route_change` navigation with the `loading_type` attribute. If an interaction on your web page leads to a different URL without a full refresh of the page, the RUM SDK starts a new view event with `loading_type:route_change`. RUM tracks URL changes using the [History API][16]. -Datadog provides a unique performance KPI, `loading_time`, which calculates the time needed for a page to load. This KPI works for both `initial_load` and `route_change` navigation. +Datadog provides a unique KPI, `loading_time`, which calculates the time needed for a page to load. This KPI works for both `initial_load` and `route_change` navigation. ### How loading time is calculated diff --git a/content/en/real_user_monitoring/browser/monitoring_resource_performance.md b/content/en/real_user_monitoring/browser/monitoring_resource_performance.md index 2788df2a8d4e7..bf84714e7c4a2 100644 --- a/content/en/real_user_monitoring/browser/monitoring_resource_performance.md +++ b/content/en/real_user_monitoring/browser/monitoring_resource_performance.md @@ -40,7 +40,7 @@ Detailed network timing data for resources is collected from the Fetch and XHR n | `resource.duration` | number | Entire time spent loading the resource. | | `resource.size` | number (bytes) | Resource size. | | `resource.connect.duration` | number (ns) | Time spent establishing a connection to the server (connectEnd - connectStart). | -| `resource.ssl.duration` | number (ns) | Time spent for the TLS handshake. If the last request is not over HTTPS, this telemetry does not appear (connectEnd - secureConnectionStart). | +| `resource.ssl.duration` | number (ns) | Time spent for the TLS handshake. If the last request is not over HTTPS, this attribute does not appear (connectEnd - secureConnectionStart). | | `resource.dns.duration` | number (ns) | Time spent resolving the DNS name of the last request (domainLookupEnd - domainLookupStart). | | `resource.redirect.duration` | number (ns) | Time spent on subsequent HTTP requests (redirectEnd - redirectStart). | | `resource.first_byte.duration` | number (ns) | Time spent waiting for the first byte of response to be received (responseStart - RequestStart). | diff --git a/content/en/real_user_monitoring/mobile_and_tv_monitoring/android/data_collected.md b/content/en/real_user_monitoring/mobile_and_tv_monitoring/android/data_collected.md index e9f7408296c19..b93c637acf0ad 100644 --- a/content/en/real_user_monitoring/mobile_and_tv_monitoring/android/data_collected.md +++ b/content/en/real_user_monitoring/mobile_and_tv_monitoring/android/data_collected.md @@ -14,11 +14,11 @@ further_reading: ## Overview -The RUM Android SDK generates events that have associated telemetry and attributes. Telemetry are quantifiable values that can be used for measurements related to the event. Attributes are non-quantifiable values used to slice telemetry values (group by) in analytics. +The RUM Android SDK generates events that have associated attributes. Those can have quantifiable values and can be used for measurements related to the event, others are non-quantifiable values used to slice telemetry values (group by) in analytics. Every RUM event has all of the [default attributes](#default-attributes), for example, the device type (`device.type`) and user information such as their name (`usr.name`) and their country (`geo.country`). -There are additional [telemetry and attributes that are specific to a given event type](#event-specific-telemetry-and-attributes). For example, the telemetry `view.time_spent` is associated with "view" events and the attribute `resource.method` is associated with "resource" events. +There are additional [attributes that are specific to a given event type](#event-specific-attributes). For example, the `view.time_spent` attribute is associated with "view" events and the `resource.method` one is associated with "resource" events. | Event Type | Retention | Description | |----------------|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| diff --git a/content/en/real_user_monitoring/platform/dashboards/performance.md b/content/en/real_user_monitoring/platform/dashboards/performance.md index 377c9ab7a55d2..313e330822291 100644 --- a/content/en/real_user_monitoring/platform/dashboards/performance.md +++ b/content/en/real_user_monitoring/platform/dashboards/performance.md @@ -20,7 +20,7 @@ further_reading: The web app performance dashboard offers a bird's-eye view of RUM web applications. It shows: - **Core web vitals**: - For all views, three browser performance KPIs are highlighted: Largest Contentful Paint, First Input Delay, and Cumulative Layout Shift. Other performance telemetry, such as Load Time, is also available. + For all views, additional browser KPIs are highlighted: Largest Contentful Paint, First Input Delay, and Cumulative Layout Shift. Other performance telemetry, such as Load Time, is also available. - **XHR and Fetch requests and resources**: For all views, identify bottlenecks when your application loads. - **Long tasks** : Events that block the browser's main thread for more than 50ms. @@ -35,7 +35,7 @@ For more information about the data displayed, see [RUM Browser Data Collected][ The mobile app performance dashboard gives an overview of RUM mobile applications. It shows: - **Mobile vitals**: - For all screens, four mobile performance KPIs are highlighted: slow renders, CPU ticks per seconds, frozen frames, and memory usage. Other performance telemetry, such as crash-free sessions, is also available. + For all screens, additional mobile KPIs are highlighted: slow renders, CPU ticks per seconds, frozen frames, and memory usage. Other performance telemetry, such as crash-free sessions, is also available. - **Resources analysis**: For all screens, identify bottlenecks when your application requests content. - **Crashes and errors**: diff --git a/content/en/real_user_monitoring/platform/dashboards/testing_and_deployment.md b/content/en/real_user_monitoring/platform/dashboards/testing_and_deployment.md index 368d9d4809e15..7e9b8a0456b70 100644 --- a/content/en/real_user_monitoring/platform/dashboards/testing_and_deployment.md +++ b/content/en/real_user_monitoring/platform/dashboards/testing_and_deployment.md @@ -43,7 +43,7 @@ For more information about the data displayed, see [RUM Browser Data Collected][ The RUM Web App Deployment Tracking dashboard helps you identify when a recent deployment is causing performance issues or new errors within your application. To use this feature, make sure that you [add RUM versions to your application][4]. This dashboard shows: - **Core web vitals**: - For all views, three browser performance KPIs are highlighted: Largest Contentful Paint, First Input Delay, and Cumulative Layout Shift. Other performance telemetry, such as Load Time, is also available. + For all views, three browser KPIs are highlighted: Largest Contentful Paint, First Input Delay, and Cumulative Layout Shift. Other performance telemetry, such as Load Time, is also available. - **Errors**: See a count of errors, percentage of views with errors, and explore ongoing issues. - **Browser performance telemetry**: @@ -64,7 +64,7 @@ This dashboard shows: - **Errors**: Review error count by version, error rate by version, and explore ongoing errors. - **Mobile vitals by version**: - For all versions, four mobile performance KPIs are highlighted: slow renders, frozen frames, application start time, and memory usage. + For all versions, additional mobile KPIs are highlighted: slow renders, frozen frames, application start time, and memory usage. {{< img src="real_user_monitoring/dashboards/dashboard-deployment-mobile.png" alt="Out-of-the-box mobile deployment dashboard" style="width:100%" >}} From a1278a42d14299187563ccaacc780c2b7936c7b1 Mon Sep 17 00:00:00 2001 From: Rosa Trieu Date: Wed, 16 Jul 2025 10:29:37 -0700 Subject: [PATCH 4/4] update android, ios, roku --- .../android/data_collected.md | 127 ++++++++---------- .../ios/data_collected.md | 104 ++++++-------- .../roku/data_collected.md | 113 +++++++--------- 3 files changed, 142 insertions(+), 202 deletions(-) diff --git a/content/en/real_user_monitoring/mobile_and_tv_monitoring/android/data_collected.md b/content/en/real_user_monitoring/mobile_and_tv_monitoring/android/data_collected.md index b93c637acf0ad..93ca381f3e5c1 100644 --- a/content/en/real_user_monitoring/mobile_and_tv_monitoring/android/data_collected.md +++ b/content/en/real_user_monitoring/mobile_and_tv_monitoring/android/data_collected.md @@ -14,14 +14,14 @@ further_reading: ## Overview -The RUM Android SDK generates events that have associated attributes. Those can have quantifiable values and can be used for measurements related to the event, others are non-quantifiable values used to slice telemetry values (group by) in analytics. +The RUM Android SDK generates events that have associated attributes. These can have quantifiable values and can be used for measurements related to the event, while others are non-quantifiable values used to slice telemetry values (group by) in analytics. Every RUM event has all of the [default attributes](#default-attributes), for example, the device type (`device.type`) and user information such as their name (`usr.name`) and their country (`geo.country`). There are additional [attributes that are specific to a given event type](#event-specific-attributes). For example, the `view.time_spent` attribute is associated with "view" events and the `resource.method` one is associated with "resource" events. -| Event Type | Retention | Description | -|----------------|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Event Type | Retention | Description | +|----------------|-----------|-------------------| | Session | 30 days | A session represents a real user journey on your mobile application. It begins when the user launches the application, and the session remains live as long as the user stays active. During the user journey, all RUM events generated as part of the session will share the same `session.id` attribute. **Note:** The session resets after 15 minutes of inactivity. If the application is killed by the OS, you can reset the session while the application is in the background. | | View | 30 days | A view represents a unique screen (or screen segment) on your mobile application. A view starts and stops when the `onActivityResumed` and `onActivityPaused` callbacks are called through the `ActivityLifecycleCallbacks` interface. Each occurrence is classified as a distinct view. While a user stays on a view, RUM event attributes (Errors, Resources, and Actions) get attached to the view with a unique `view.id`. | | Resource | 15 days | A resource represents network requests to first-party hosts, APIs, and third-party providers in your mobile application. All requests generated during a user session are attached to the view with a unique `resource.id`. | @@ -48,7 +48,7 @@ The Android RUM SDK offers various strategies to [automatically track views][2] - Activities (`ActivityViewTrackingStrategy`): When you rely on this strategy, the SDK automatically starts a RUM view when the Activity enters the foreground (`onResume`) and stops it when the Activity leaves the foreground (`onPause`). - Fragments (`FragmentViewTrackingStrategy`): Each `Fragment` in your application is tracked as a separate RUM view. The SDK starts the view in the Fragment's `onResume` lifecycle method and stops it in `onPause`. -Mixed (`MixedViewTrackingStrategy`): Activities and Fragments each become distinct RUM views based on their respective lifecycle events (`onResume` and `onPause`). +- Mixed (`MixedViewTrackingStrategy`): Activities and Fragments each become distinct RUM views based on their respective lifecycle events (`onResume` and `onPause`). - Navigation (`NavigationViewTrackingStrategy`): Each navigation destination is treated as a distinct RUM view, so view boundaries align with navigation events in your graph. - Manual View Tracking: When [tracking views manually][3] using `GlobalRumMonitor` APIs, the view starts precisely when you call the `startView(...)` method and stops when you call the `stopView()` method. @@ -64,11 +64,11 @@ RUM collects common attributes for all events and attributes specific to each ev | Attribute name | Type | Description | |------------------|--------|-----------------------------| -| `date` | integer | Start of the event in milliseconds from epoch. | -| `type` | string | The type of the event (for example, `view` or `resource`). | -| `service` | string | The [unified service name][8] for this application used to correlate user sessions. | | `application.id` | string | The Datadog application ID. | | `application.name` | string | The Datadog application name. | +| `date` | integer | Start of the event in milliseconds from epoch. | +| `service` | string | The [unified service name][8] for this application used to correlate user sessions. | +| `type` | string | The type of the event (for example, `view` or `resource`). | ### Device @@ -76,11 +76,11 @@ The following device-related attributes are attached automatically to all events | Attribute name | Type | Description | |------------------------------------------|--------|-------------------------------------------------| -| `device.type` | string | The device type as reported by the device (System User-Agent). | +| `device.architecture` | string | The CPU architecture of the device that is reporting the error. | | `device.brand` | string | The device brand as reported by the device (System User-Agent). | | `device.model` | string | The device model as reported by the device (System User-Agent). | | `device.name` | string | The device name as reported by the device (System User-Agent). | -| `device.architecture` | string | The CPU architecture of the device that is reporting the error. | +| `device.type` | string | The device type as reported by the device (System User-Agent). | ### Connectivity @@ -88,10 +88,10 @@ The following network-related attributes are attached automatically to Resource | Attribute name | Type | Description | |------------------------------------------|--------|-------------------------------------------------| -| `connectivity.status` | string | Status of device network reachability (`connected`, `not connected`, or `maybe`). | -| `connectivity.interfaces` | string | The list of available network interfaces (for example, `bluetooth`, `cellular`, `ethernet`, or `wifi`). | -| `connectivity.cellular.technology` | string | The type of a radio technology used for cellular connection. | | `connectivity.cellular.carrier_name` | string | The name of the SIM carrier. | +| `connectivity.cellular.technology` | string | The type of a radio technology used for cellular connection. | +| `connectivity.interfaces` | string | The list of available network interfaces (for example, `bluetooth`, `cellular`, `ethernet`, or `wifi`). | +| `connectivity.status` | string | Status of device network reachability (`connected`, `not connected`, or `maybe`). | ### Operating system @@ -105,7 +105,7 @@ The following OS-related attributes are attached automatically to all events col ### Geo-location -The below attributes are related to the geo-location of IP addresses. +The following attributes are related to the geo-location of IP addresses. **Note:** If you want to stop collecting geo-location attributes, change the setting in your [application details][9]. @@ -117,97 +117,83 @@ The below attributes are related to the geo-location of IP addresses. | `geo.continent_code` | string | ISO code of the continent (`EU`, `AS`, `NA`, `AF`, `AN`, `SA`, or `OC`). | | `geo.continent` | string | Name of the continent (`Europe`, `Australia`, `North America`, `Africa`, `Antarctica`, `South America`, or `Oceania`). | | `geo.city` | string | The name of the city (for example, `San Francisco`, `Paris`, or `New York`). | + ### Global user attributes You can enable [tracking user info][10] globally to collect and apply user attributes to all RUM events. | Attribute name | Type | Description | |------------------|--------|-----------------------------| +| `usr.email` | string | Email of the user. | | `user.id` | string | Identifier of the user. | | `usr.name` | string | Name of the user. | -| `usr.email` | string | Email of the user. | -## Event-specific telemetry and attributes +## Event-specific attributes Telemetry are quantifiable values that can be used for measurements related to the event. Attributes are non-quantifiable values used to slice telemetry values (group by) in analytics. -### Session KPIs +### Session attributes -| KPI | Type | Description | +| Attribute | Type | Description | |------------|--------|----------------------------| -| `session.time_spent` | number (ns) | Time spent on a session. | -| `session.view.count` | number | Count of all views collected for this session. | -| `session.error.count` | number | Count of all errors collected for this session. | -| `session.resource.count` | number | Count of all resources collected for this session. | | `session.action.count` | number | Count of all actions collected for this session. | -| `session.long_task.count` | number | Count of all long tasks collected for this session. - -### Session attributes - -| Attribute name | Type | Description | -|--------------------------------|--------|----------------------------------------------------------------------------------------------------------------| +| `session.error.count` | number | Count of all errors collected for this session. | +| `session.has_replay` | boolean | Indicates if the session has a captured Session Replay recording attached to visually play the user experience. | | `session.id` | string | Unique ID of the session. | -| `session.type` | string | Type of the session (`user`). | -| `session.is_active` | boolean | Indicates if the session is currently active. The session ends if a user navigates away from the application or closes the browser window, and expires after 4 hours of activity or 15 minutes of inactivity. | -| `session.initial_view.url` | string | URL of the initial view of the session. | +| `session.ip` | string | IP address of the session extracted from the TCP connection of the intake. If you want to stop collecting this attribute, change the setting in your [application details][11]. | +| `session.is_active` | boolean | Indicates if the session is currently active. The session ends if a user navigates away from the application or closes the application, and expires after 4 hours of activity or 15 minutes of inactivity. | | `session.initial_view.name` | string | Name of the initial view of the session. | +| `session.initial_view.url` | string | URL of the initial view of the session. | | `session.last_view.url` | string | URL of the last view of the session. | | `session.last_view.name` | string | Name of the last view of the session. | -| `session.ip` | string | IP address of the session extracted from the TCP connection of the intake. If you want to stop collecting this attribute, change the setting in your [application details][11]. | -| `session.useragent` | string | System user agent info to interpret device info. | -| `session.has_replay` | boolean | Indicates if the session has a captured Session Replay recording attached to visually play the user experience. | +| `session.long_task.count` | number | Count of all long tasks collected for this session. | +| `session.resource.count` | number | Count of all resources collected for this session. | +| `session.type` | string | Type of the session (`user`). | +| `session.time_spent` | number (ns) | Time spent on a session. | +| `session.view.count` | number | Count of all views collected for this session. | +| `session.useragent` | string | System user agent info to interpret device info. | -### View telemetry +### View attributes RUM action, error, resource, and long task events contain information about the active RUM view event at the time of collection. -| Telemetry | Type | Description | +| Attribute | Type | Description | |----------------------------------------|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| `view.time_spent` | number (ns) | Time spent on this view. | -| `view.long_task.count` | number | Count of all long tasks collected for this view. | -| `view.error.count` | number | Count of all errors collected for this view. | -| `view.resource.count` | number | Count of all resources collected for this view. | | `view.action.count` | number | Count of all actions collected for this view. | +| `view.error.count` | number | Count of all errors collected for this view. | +| `view.id` | string | Unique ID of the initial view corresponding to the event. | +| `view.interaction_to_next_view_time` | number (ns) | Time between the last user interaction in the previous and start of this (current) view. | | `view.is_active` | boolean | Indicates whether the view corresponding to this event is considered active. | | `view.loading_time` | number (ns) | Time it took for the view to load, set by the `addViewLoadingTime(override:)` call. | +| `view.long_task.count` | number | Count of all long tasks collected for this view. | +| `view.name` | string | Customizable name of the view corresponding to the event. | | `view.network_settled_time` | number (ns) | Time it took for a view to be fully loaded with all relevant network calls initiated at the start of the view. | -| `view.interaction_to_next_view_time` | number (ns) | Time between the last user interaction in the previous and start of this (current) view. | - -### View attributes - -| Attribute name | Type | Description | -|--------------------------------|--------|----------------------------------------------------------------------------------------------------------------| -| `view.id` | string | Unique ID of the initial view corresponding to the event. | +| `view.resource.count` | number | Count of all resources collected for this view. | +| `view.time_spent` | number (ns) | Time spent on this view. | | `view.url` | string | Canonical name of the class corresponding to the event. | -| `view.name` | string | Customizable name of the view corresponding to the event. | -### Resource telemetry +### Resource attributes -| Telemetry | Type | Description | +| Attribute | Type | Description | |----------------------------------------|----------------|-------------------------------------------------------------------------------------------------------------------------------------------| -| `resource.duration` | number (ns) | Entire time spent loading the resource. | -| `resource.size` | number (bytes) | Resource size. | | `resource.connect.duration` | number (ns) | Time spent establishing a connection to the server (connectEnd - connectStart). | -| `resource.ssl.duration` | number (ns) | Time spent for the TLS handshake. If the last request is not over HTTPS, this telemetry does not appear (connectEnd - secureConnectionStart). | | `resource.dns.duration` | number (ns) | Time spent resolving the DNS name of the last request (domainLookupEnd - domainLookupStart). | -| `resource.redirect.duration` | number (ns) | Time spent on subsequent HTTP requests (redirectEnd - redirectStart). | -| `resource.first_byte.duration` | number (ns) | Time spent waiting for the first byte of response to be received (responseStart - RequestStart). | | `resource.download.duration` | number (ns) | Time spent downloading the response (responseEnd - responseStart). | - -### Resource attributes - -| Attribute | Type | Description | -|--------------------------------|--------|-----------------------------------------------------------------------------------------| +| `resource.duration` | number (ns) | Entire time spent loading the resource. | +| `resource.first_byte.duration` | number (ns) | Time spent waiting for the first byte of response to be received (responseStart - requestStart). | | `resource.id` | string | Unique identifier of the resource. | -| `resource.type` | string | The type of resource being collected (for example, `xhr`, `image`, `font`, `css`, or `js`). | | `resource.method` | string | The HTTP method (for example, `POST`, `GET`, `PATCH`, or `DELETE`). | -| `resource.status_code` | number | The response status code. | -| `resource.url` | string | The resource URL. | -| `resource.provider.name` | string | The resource provider name. Default is `unknown`. | | `resource.provider.domain` | string | The resource provider domain. | +| `resource.provider.name` | string | The resource provider name. Default is `unknown`. | | `resource.provider.type` | string | The resource provider type (for example, `first-party`, `cdn`, `ad`, or `analytics`). | +| `resource.redirect.duration` | number (ns) | Time spent on subsequent HTTP requests (redirectEnd - redirectStart). | +| `resource.size` | number (bytes) | Resource size. | +| `resource.ssl.duration` | number (ns) | Time spent for the TLS handshake. If the last request is not over HTTPS, this attribute does not appear (connectEnd - secureConnectionStart). | +| `resource.status_code` | number | The response status code. | +| `resource.type` | string | The type of resource being collected (for example, `xhr`, `image`, `font`, `css`, or `js`). | +| `resource.url` | string | The resource URL. | ### Error attributes @@ -219,7 +205,7 @@ Front-end errors are collected with Real User Monitoring (RUM). The error messag | `error.type` | string | The error type (or error code in some cases). | | `error.message` | string | A concise, human-readable one-line message explaining the event. | | `error.stack` | string | The stack trace or complementary information about the error. | -| `error.issue_id` | string | The stack trace or complementary information about the error. | +| `error.issue_id` | string | Unique identifier for the error issue. | | `error.category` | string | The high-level grouping for the type of error. Possible values are `ANR` or `Exception` | | `error.file` | string | File where the error happened for the Error Tracking issue. | | `error.is_crash` | boolean | Indicates whether the error caused the application to crash. | @@ -237,14 +223,14 @@ Network errors include information about failing HTTP requests. The following fa | `error.resource.provider.domain` | string | The resource provider domain. | | `error.resource.provider.type` | string | The resource provider type (for example, `first-party`, `cdn`, `ad`, or `analytics`). | -### Action timing telemetry +### Action timing attributes -| Telemetry | Type | Description | +| Attribute | Type | Description | |--------------|--------|--------------------------| | `action.loading_time` | number (ns) | The loading time of the action. | | `action.long_task.count` | number | Count of all long tasks collected for this action. | | `action.resource.count` | number | Count of all resources collected for this action. | -| `action.error.count` | number | Count of all errors collected for this action.| +| `action.error.count` | number | Count of all errors collected for this action. | ### Action attributes @@ -257,7 +243,7 @@ Network errors include information about failing HTTP requests. The following fa ## Data storage -Before data is uploaded to Datadog, it is stored in cleartext in your application's cache directory. This cache folder is protected by [Android's Application Sandbox][12], meaning that on most devices, this data can't be read by other applications. However, if the mobile device is rooted, or someone tempers with the Linux kernel, the stored data might become readable. +Before data is uploaded to Datadog, it is stored in cleartext in your application's cache directory. This cache folder is protected by [Android's Application Sandbox][12], meaning that on most devices, this data can't be read by other applications. However, if the mobile device is rooted, or someone tampers with the Linux kernel, the stored data might become readable. ## Data upload @@ -265,15 +251,14 @@ The RUM Android SDK allows you to get the data you need to Datadog while conside - On _event collected_, the Datadog SDK appends uncompressed events to a batch file (using a tag-length-value, or TLV encoding format) - On _upload_ (when the batch is considered "closed"), the Datadog SDK: - - Reads the batch and extract events + - Reads the batch and extracts events - Drops redundant View events in RUM (no optimizations in other tracks) - Builds payloads specific to each track - Compresses the payload and sends it ## Direct Boot mode support -If your application supports [Direct Boot mode][13], note that data captured before the device -is unlocked won't be captured, since the credential encrypted storage won't be available yet. +If your application supports [Direct Boot mode][13], note that data captured before the device is unlocked won't be captured, since the credential encrypted storage won't be available yet. ## Further Reading diff --git a/content/en/real_user_monitoring/mobile_and_tv_monitoring/ios/data_collected.md b/content/en/real_user_monitoring/mobile_and_tv_monitoring/ios/data_collected.md index e94dac59da7b4..bf28d8df2fd50 100644 --- a/content/en/real_user_monitoring/mobile_and_tv_monitoring/ios/data_collected.md +++ b/content/en/real_user_monitoring/mobile_and_tv_monitoring/ios/data_collected.md @@ -18,7 +18,7 @@ The RUM iOS SDK generates events that have associated telemetry and attributes. Every RUM event has all of the [default attributes](#default-attributes), for example, the device type (`device.type`) and user information such as their name (`usr.name`) and their country (`geo.country`). -There are additional [telemetry and attributes that are specific to a given event type](#event-specific-telemetry-and-attributes). For example, the telemetry `view.time_spent` is associated with "view" events and the attribute `resource.method` is associated with "resource" events. +There are additional [attributes specific to a given event type](#event-specific-attributes). For example, the `view.loading_time` telemetry is associated with view events, and the `resource.method` attribute is associated with resource events. | Event Type | Retention | Description | |------------|-----------|-------------------------------------| @@ -65,7 +65,7 @@ RUM collects common attributes for all events and attributes specific to each ev |------------------|---------|------------------------------------------------------------------------------------| | `date` | integer | Start of the event in milliseconds from epoch. | | `type` | string | The type of the event (for example, `view` or `resource`). | -| `service` | string | The [unified service name][7] for this application used to corelate user sessions. | +| `service` | string | The [unified service name][7] for this application used to correlate user sessions. | | `application.id` | string | The Datadog application ID. | | `application.name` | string | The Datadog application name. | @@ -89,7 +89,7 @@ The following network-related attributes are attached automatically to Resource |------------------------------------------|--------|-------------------------------------------------| | `connectivity.status` | string | Status of device network reachability (`connected`, `not connected`, `maybe`). | | `connectivity.interfaces` | string | The list of available network interfaces (for example, `bluetooth`, `cellular`, `ethernet`, or `wifi`). | -| `connectivity.cellular.technology` | string | The type of a radio technology used for cellular connection. | +| `connectivity.cellular.technology` | string | The type of radio technology used for cellular connection. | | `connectivity.cellular.carrier_name` | string | The name of the SIM carrier. | @@ -106,7 +106,7 @@ The following OS-related attributes are attached automatically to all events col ### Geo-location -The below attributes are related to the geo-location of IP addresses. +The following attributes are related to the geo-location of IP addresses. **Note:** If you want to stop collecting geo-location attributes, change the setting in your [application details][8]. @@ -131,86 +131,67 @@ You can enable [tracking user info][7] globally to collect and apply user attrib | `usr.email` | string | Email of the user. | -## Event-specific telemetry and attributes +## Event-specific attributes -### Session KPIs +### Session attributes -| KPI | Type | Description | +| Attribute | Type | Description | |---------------------------|-------------|-----------------------------------------------------| -| `session.time_spent` | number (ns) | Time spent on a session. | -| `session.view.count` | number | Count of all views collected for this session. | -| `session.error.count` | number | Count of all errors collected for this session. | -| `session.resource.count` | number | Count of all resources collected for this session. | | `session.action.count` | number | Count of all actions collected for this session. | +| `session.error.count` | number | Count of all errors collected for this session. | | `session.long_task.count` | number | Count of all long tasks collected for this session. | | `session.has_replay` | boolean | Indicates if the session has a captured Session Replay recording attached to visually play the user experience. | - - -### Session attributes - -| Attribute name | Type | Description | -|------------------------------|--------|----------------------------------------------------------------------------| | `session.id` | string | Unique ID of the session. | -| `session.type` | string | Type of the session (`user`). | -| `session.is_active` | boolean | Indicates if the session is currently active. The session ends if a user navigates away from the application or closes the browser window, and expires after 4 hours of activity or 15 minutes of inactivity. | | `session.initial_view.url` | string | URL of the initial view of the session. | | `session.initial_view.name` | string | Name of the initial view of the session. | +| `session.ip` | string | IP address of the session extracted from the TCP connection of the intake. If you want to stop collecting this attribute, change the setting in your [application details][9]. | +| `session.is_active` | boolean | Indicates if the session is currently active. The session ends if a user navigates away from the application or closes the browser window, and expires after 4 hours of activity or 15 minutes of inactivity. | | `session.last_view.url` | string | URL of the last view of the session. | | `session.last_view.name` | string | Name of the last view of the session. | -| `session.ip` | string | IP address of the session extracted from the TCP connection of the intake. If you want to stop collecting this attribute, change the setting in your [application details][9]. | +| `session.resource.count` | number | Count of all resources collected for this session. | +| `session.time_spent` | number (ns) | Time spent on a session. | +| `session.type` | string | Type of the session (`user`). | | `session.useragent` | string | System user agent info to interpret device info. | +| `session.view.count` | number | Count of all views collected for this session. | - -### View telemetry +### View attributes RUM action, error, resource, and long task events contain information about the active RUM view event at the time of collection. -| Telemetry | Type | Description | +| Attribute | Type | Description | |-----------------------|-------------|------------------------------------------------------------------------------| -| `view.time_spent` | number (ns) | Time spent on this view. | -| `view.long_task.count` | number | Count of all long tasks collected for this view. | -| `view.error.count` | number | Count of all errors collected for this view. | -| `view.resource.count` | number | Count of all resources collected for this view. | | `view.action.count` | number | Count of all actions collected for this view. | +| `view.error.count` | number | Count of all errors collected for this view. | | `view.is_active` | boolean | Indicates whether the view corresponding to this event is considered active. | - -### View attributes - -| Attribute name | Type | Description | -|----------------|--------|-----------------------------------------------------------------| | `view.id` | string | Unique ID of the initial view corresponding to the event. | -| `view.url` | string | URL of the `UIViewController` class corresponding to the event. | -| `view.name` | string | Customizable name of the view corresponding to the event. | | `view.loading_time` | number (ns) | Time it took for the view to load, set by addViewLoadingTime(override:) call. | -| `view.network_settled_time` | number (ns) | Time it took for a view to be fully initiated at the start of the view. | +| `view.long_task.count` | number | Count of all long tasks collected for this view. | | `view.interaction_to_next_view_time` | number (ns) | Time between the last user interaction in the previous view and start of this (current) view. | +| `view.name` | string | Customizable name of the view corresponding to the event. | +| `view.network_settled_time` | number (ns) | Time it took for a view to be fully initiated at the start of the view. | +| `view.resource.count` | number | Count of all resources collected for this view. | +| `view.time_spent` | number (ns) | Time spent on this view. | +| `view.url` | string | URL of the `UIViewController` class corresponding to the event. | -### Resource telemetry - -| Telemetry | Type | Description | +### Resource attributes +| Attribute | Type | Description | |--------------------------------|----------------|-------------------------------------------------------------------------------------------------| -| `resource.duration` | number | Entire time spent loading the resource. | -| `resource.size` | number (bytes) | Resource size. | | `resource.connect.duration` | number (ns) | Time spent establishing a connection to the server (connectEnd - connectStart). | -| `resource.ssl.duration` | number (ns) | Time spent for the TLS handshake. | | `resource.dns.duration` | number (ns) | Time spent resolving the DNS name of the last request (domainLookupEnd - domainLookupStart). | -| `resource.redirect.duration` | number (ns) | Time spent on subsequent HTTP requests (redirectEnd - redirectStart). | -| `resource.first_byte.duration` | number (ns) | Time spent waiting for the first byte of response to be received (responseStart - requestStart). | | `resource.download.duration` | number (ns) | Time spent downloading the response (responseEnd - responseStart). | - -### Resource attributes - -| Attribute | Type | Description | -|----------------------------|--------|------------------------------------------------------------------------------------------| +| `resource.duration` | number | Entire time spent loading the resource. | +| `resource.first_byte.duration` | number (ns) | Time spent waiting for the first byte of response to be received (responseStart - requestStart). | | `resource.id` | string | Unique identifier of the resource. | -| `resource.type` | string | The type of resource being collected (for example, `xhr`, `image`, `font`, `css`, or `js`). | | `resource.method` | string | The HTTP method (for example, `POST`, `GET`, `PATCH`, or `DELETE`). | -| `resource.status_code` | number | The response status code. | -| `resource.url` | string | The resource URL. | | `resource.provider.name` | string | The resource provider name. Default is `unknown`. | | `resource.provider.domain` | string | The resource provider domain. | | `resource.provider.type` | string | The resource provider type (for example, `first-party`, `cdn`, `ad`, or `analytics`). | - +| `resource.redirect.duration` | number (ns) | Time spent on subsequent HTTP requests (redirectEnd - redirectStart). | +| `resource.size` | number (bytes) | Resource size. | +| `resource.ssl.duration` | number (ns) | Time spent for the TLS handshake. | +| `resource.status_code` | number | The response status code. | +| `resource.type` | string | The type of resource being collected (for example, `xhr`, `image`, `font`, `css`, or `js`). | +| `resource.url` | string | The resource URL. | ### Error attributes @@ -242,25 +223,20 @@ Network errors include information about failing HTTP requests. The following fa | `error.resource.provider.type` | string | The resource provider type (for example, `first-party`, `cdn`, `ad`, or `analytics`). | -### Action telemetry +### Action attributes -| Telemetry | Type | Description | +| Attribute | Type | Description | |-------------------------|-------------|-----------------------------------------------| -| `action.loading_time` | number (ns) | The loading time of the action. | -| `action.long_task.count` | number | Count of all long tasks collected for this action. | -| `action.resource.count` | number | Count of all resources issued by this action. | | `action.error.count` | number | Count of all errors issued by this action. | - -### Action attributes - -| Attribute | Type | Description | -|----------------------|--------|---------------------------------------------------------------------------------| | `action.id` | string | UUID of the user action. | -| `action.type` | string | Type of the user action (for example, `tap` or `application_start`). | +| `action.loading_time` | number (ns) | The loading time of the action. | +| `action.long_task.count` | number | Count of all long tasks collected for this action. | | `action.name` | string | Name of the user action. | +| `action.resource.count` | number | Count of all resources issued by this action. | | `action.target.name` | string | Element that the user interacted with. Only for automatically collected actions. | +| `action.type` | string | Type of the user action (for example, `tap` or `application_start`). | -## Data Storage +## Data storage Before data is uploaded to Datadog, it is stored in cleartext in the cache directory (`Library/Caches`) of your [application sandbox][10], which can't be read by any other app installed on the device. diff --git a/content/en/real_user_monitoring/mobile_and_tv_monitoring/roku/data_collected.md b/content/en/real_user_monitoring/mobile_and_tv_monitoring/roku/data_collected.md index b426022055592..90dfb06104b96 100644 --- a/content/en/real_user_monitoring/mobile_and_tv_monitoring/roku/data_collected.md +++ b/content/en/real_user_monitoring/mobile_and_tv_monitoring/roku/data_collected.md @@ -15,11 +15,11 @@ site_support_id: rum_roku ## Overview -The RUM Roku SDK generates events that have associated telemetry and attributes. Telemetry are quantifiable values that can be used for measurements related to the event. Attributes are non-quantifiable values used to slice telemetry values (group by) in analytics. +The RUM Roku SDK generates events that have associated telemetry and attributes. Telemetry is quantifiable values that can be used for measurements related to the event. Attributes are non-quantifiable values used to slice telemetry values (group by) in analytics. Every RUM event has all of the [default attributes](#default-attributes), for example, the device type (`device.type`) and user information such as their name (`usr.name`) and their country (`geo.country`). -There are additional [telemetry and attributes that are specific to a given event type](#event-specific-telemetry-and-attributes). For example, the telemetry `view.time_spent` is associated with "view" events and the attribute `resource.method` is associated with "resource" events. +There are additional [attributes specific to a given event type](#event-specific-attributes). For example, the `view.loading_time` telemetry is associated with view events, and the `resource.method` attribute is associated with resource events. | Event Type | Retention | Description | | ---------- | --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | @@ -97,83 +97,66 @@ You can enable [tracking user info][5] globally to collect and apply user attrib | `usr.email` | string | Email of the user. | -## Event-specific telemetry and attributes +## Event-specific attributes -Telemetry are quantifiable values that can be used for measurements related to the event. Attributes are non-quantifiable values used to slice telemetry values (group by) in analytics. +Telemetry is quantifiable values that can be used for measurements related to the event. Attributes are non-quantifiable values used to slice telemetry values (group by) in analytics. -### Session KPIs +### Session attributes -| KPI | Type | Description | +| Attribute name | Type | Description | | ------------------------- | ----------- | --------------------------------------------------- | -| `session.time_spent` | number (ns) | Time spent on a session. | -| `session.view.count` | number | Count of all views collected for this session. | -| `session.error.count` | number | Count of all errors collected for this session. | -| `session.resource.count` | number | Count of all resources collected for this session. | | `session.action.count` | number | Count of all actions collected for this session. | -| `session.long_task.count` | number | Count of all long tasks collected for this session. | - -### Session attributes - -| Attribute name | Type | Description | -| --------------------------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `session.error.count` | number | Count of all errors collected for this session. | | `session.id` | string | Unique ID of the session. | -| `session.type` | string | Type of the session (`user`). | -| `session.is_active` | boolean | Indicates if the session is currently active. The session ends if a user navigates away from the application or closes the browser window, and expires after 4 hours of activity or 15 minutes of inactivity. | -| `session.initial_view.url` | string | URL of the initial view of the session. | | `session.initial_view.name` | string | Name of the initial view of the session. | -| `session.last_view.url` | string | URL of the last view of the session. | -| `session.last_view.name` | string | Name of the last view of the session. | +| `session.initial_view.url` | string | URL of the initial view of the session. | | `session.ip` | string | IP address of the session extracted from the TCP connection of the intake. If you want to stop collecting this attribute, change the setting in your [application details][8]. | +| `session.is_active` | boolean | Indicates if the session is currently active. The session ends if a user navigates away from the application or closes the browser window, and expires after 4 hours of activity or 15 minutes of inactivity. | +| `session.last_view.name` | string | Name of the last view of the session. | +| `session.last_view.url` | string | URL of the last view of the session. | +| `session.long_task.count` | number | Count of all long tasks collected for this session. | +| `session.resource.count` | number | Count of all resources collected for this session. | +| `session.time_spent` | number (ns) | Time spent on a session. | +| `session.type` | string | Type of the session (`user`). | | `session.useragent` | string | System user agent info to interpret device info. | +| `session.view.count` | number | Count of all views collected for this session. | -### View telemetry +### View attributes RUM action, error, resource, and long task events contain information about the active RUM view event at the time of collection. - -| Telemetry | Type | Description | +| Attribute | Type | Description | | ---------------------- | ----------- | ---------------------------------------------------------------------------- | -| `view.time_spent` | number (ns) | Time spent on this view. | -| `view.long_task.count` | number | Count of all long tasks collected for this view. | -| `view.error.count` | number | Count of all errors collected for this view. | -| `view.resource.count` | number | Count of all resources collected for this view. | | `view.action.count` | number | Count of all actions collected for this view. | -| `view.is_active` | boolean | Indicates whether the view corresponding to this event is considered active. | - -### View attributes - -| Attribute name | Type | Description | -| -------------- | ------ | --------------------------------------------------------- | +| `view.error.count` | number | Count of all errors collected for this view. | | `view.id` | string | Unique ID of the initial view corresponding to the event. | -| `view.url` | string | Canonical name of the class corresponding to the event. | +| `view.is_active` | boolean | Indicates whether the view corresponding to this event is considered active. | +| `view.long_task.count` | number | Count of all long tasks collected for this view. | | `view.name` | string | Customizable name of the view corresponding to the event. | +| `view.resource.count` | number | Count of all resources collected for this view. | +| `view.time_spent` | number (ns) | Time spent on this view. | +| `view.url` | string | Canonical name of the class corresponding to the event. | -### Resource telemetry - +### Resource attributes -| Telemetry | Type | Description | +| Attribute name | Type | Description | | ------------------------------ | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------ | -| `resource.duration` | number (ns) | Entire time spent loading the resource. | -| `resource.size` | number (bytes) | Resource size. | | `resource.connect.duration` | number (ns) | Time spent establishing a connection to the server (connectEnd - connectStart). | -| `resource.ssl.duration` | number (ns) | Time spent for the TLS handshake. If the last request is not over HTTPS, this telemetry does not appear (connectEnd - secureConnectionStart). | | `resource.dns.duration` | number (ns) | Time spent resolving the DNS name of the last request (domainLookupEnd - domainLookupStart). | -| `resource.redirect.duration` | number (ns) | Time spent on subsequent HTTP requests (redirectEnd - redirectStart). | -| `resource.first_byte.duration` | number (ns) | Time spent waiting for the first byte of response to be received (responseStart - RequestStart). | | `resource.download.duration` | number (ns) | Time spent downloading the response (responseEnd - responseStart). | - -### Resource attributes - -| Attribute | Type | Description | -| -------------------------- | ------ | ------------------------------------------------------------------------------------------- | +| `resource.duration` | number (ns) | Entire time spent loading the resource. | +| `resource.first_byte.duration` | number (ns) | Time spent waiting for the first byte of response to be received (responseStart - RequestStart). | | `resource.id` | string | Unique identifier of the resource. | -| `resource.type` | string | The type of resource being collected (for example, `xhr`, `image`, `font`, `css`, or `js`). | | `resource.method` | string | The HTTP method (for example, `POST`, `GET`, `PATCH`, or `DELETE`). | -| `resource.status_code` | number | The response status code. | -| `resource.url` | string | The resource URL. | -| `resource.provider.name` | string | The resource provider name. Default is `unknown`. | | `resource.provider.domain` | string | The resource provider domain. | +| `resource.provider.name` | string | The resource provider name. Default is `unknown`. | | `resource.provider.type` | string | The resource provider type (for example, `first-party`, `cdn`, `ad`, or `analytics`). | +| `resource.redirect.duration` | number (ns) | Time spent on subsequent HTTP requests (redirectEnd - redirectStart). | +| `resource.size` | number (bytes) | Resource size. | +| `resource.ssl.duration` | number (ns) | Time spent for the TLS handshake. If the last request is not over HTTPS, this attribute does not appear (connectEnd - secureConnectionStart). | +| `resource.status_code` | number | The response status code. | +| `resource.type` | string | The type of resource being collected (for example, `xhr`, `image`, `font`, `css`, or `js`). | +| `resource.url` | string | The resource URL. | ### Error attributes @@ -185,8 +168,7 @@ Front-end errors are collected with Real User Monitoring (RUM). The error messag | `error.type` | string | The error type (or error code in some cases). | | `error.message` | string | A concise, human-readable one-line message explaining the event. | | `error.stack` | string | The stack trace or complementary information about the error. | -| `error.issue_id` | string | The stack trace or complementary information about the error. | - +| `error.issue_id` | string | The unique identifier for the error issue. | ### Network errors @@ -201,27 +183,24 @@ Network errors include information about failing HTTP requests. The following fa | `error.resource.provider.domain` | string | The resource provider domain. | | `error.resource.provider.type` | string | The resource provider type (for example, `first-party`, `cdn`, `ad`, or `analytics`). | -### Action timing telemetry +### Action timing attributes -| Telemetry | Type | Description | +| Attribute name | Type | Description | | ------------------------ | ----------- | -------------------------------------------------- | -| `action.loading_time` | number (ns) | The loading time of the action. | -| `action.long_task.count` | number | Count of all long tasks collected for this action. | -| `action.resource.count` | number | Count of all resources collected for this action. | | `action.error.count` | number | Count of all errors collected for this action. | - -### Action attributes - -| Attribute | Type | Description | -| -------------------- | ------ | -------------------------------------------------------------------------------- | | `action.id` | string | UUID of the user action. | -| `action.type` | string | Type of the user action (for example, `tap` or `application_start`). | +| `action.loading_time` | number (ns) | The loading time of the action. | +| `action.long_task.count` | number | Count of all long tasks collected for this action. | | `action.name` | string | Name of the user action. | +| `action.resource.count` | number | Count of all resources collected for this action. | | `action.target.name` | string | Element that the user interacted with. Only for automatically collected actions. | +| `action.type` | string | Type of the user action (for example, `tap` or `application_start`). | + +## Data storage -## Data Storage +Before data is uploaded to Datadog, it is stored in cleartext in your channel's [cache directory][6], meaning that this data can't be read by other applications. -Before data is uploaded to Datadog, it is stored in cleartext in your channel's [cache directory][6], meaning that this data can't be read by other applications. Note that the OS can evict the data at any time, which could result in data loss in some rare cases. +**Note**: The OS can evict the data at any time, which could result in data loss in some rare cases. ## Further Reading