From da0a34e6611b6748306cbe7b5acdeff130dcc1df Mon Sep 17 00:00:00 2001 From: Pedro Lousada Date: Wed, 10 Aug 2022 11:17:25 +0100 Subject: [PATCH 1/2] Replace references to iOS classes with correct Android equivalents. --- docs/mobile_data_collected.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/mobile_data_collected.md b/docs/mobile_data_collected.md index 1eb2544436..204855ce90 100644 --- a/docs/mobile_data_collected.md +++ b/docs/mobile_data_collected.md @@ -11,7 +11,7 @@ There are additional [metrics and attributes that are specific to a given event | 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 `viewDidAppear(animated:)` and `viewDidDisappear(animated:)` callbacks on the `UIViewController` class are notified. Individual `ViewControllers` are classified as distinct views. While a user stays on a view, RUM event attributes (Errors, Resources, Actions) get attached to the view with a unique `view.id`. | +| 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 via the `ActivityLifecycleCallbacks` interface. Individual `Activity` are classified as distinct views. While a user stays on a view, RUM event attributes (Errors, Resources, 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`. | | Error | 30 days | An error represents an exception or crash emitted by the mobile application attached to the view it is generated in. | | Action | 30 days | An action represents user activity in your mobile application (application launch, tap, swipe, back etc). Each action is attached with a unique `action.id` attached to the view it gets generated in. | @@ -136,7 +136,7 @@ RUM action, error, resource, and long task events contain information about the | 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.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 From 5bac9975c6a351e3605e1621bb45b195edf69508 Mon Sep 17 00:00:00 2001 From: Pedro lousada Date: Thu, 11 Aug 2022 11:20:17 +0200 Subject: [PATCH 2/2] Update docs/mobile_data_collected.md Co-authored-by: Bryce Eadie --- docs/mobile_data_collected.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/mobile_data_collected.md b/docs/mobile_data_collected.md index 204855ce90..3f08052aa7 100644 --- a/docs/mobile_data_collected.md +++ b/docs/mobile_data_collected.md @@ -11,7 +11,7 @@ There are additional [metrics and attributes that are specific to a given event | 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 via the `ActivityLifecycleCallbacks` interface. Individual `Activity` are classified as distinct views. While a user stays on a view, RUM event attributes (Errors, Resources, Actions) get attached to the view with a unique `view.id`. | +| 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, 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`. | | Error | 30 days | An error represents an exception or crash emitted by the mobile application attached to the view it is generated in. | | Action | 30 days | An action represents user activity in your mobile application (application launch, tap, swipe, back etc). Each action is attached with a unique `action.id` attached to the view it gets generated in. |