From f59f19348f22091e0b2c3cc875aa44fa123bdae2 Mon Sep 17 00:00:00 2001 From: Maciek Grzybowski Date: Fri, 18 Jul 2025 12:33:21 +0200 Subject: [PATCH 1/4] Clarify SDK and RUM initialization timing requirements in docs --- .../mobile_and_tv_monitoring/ios/setup.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/content/en/real_user_monitoring/mobile_and_tv_monitoring/ios/setup.md b/content/en/real_user_monitoring/mobile_and_tv_monitoring/ios/setup.md index 5d01d1ccb0373..4c36c7680f6eb 100644 --- a/content/en/real_user_monitoring/mobile_and_tv_monitoring/ios/setup.md +++ b/content/en/real_user_monitoring/mobile_and_tv_monitoring/ios/setup.md @@ -131,7 +131,11 @@ For more information about setting up a client token, see the [Client token docu ### Step 3 - Initialize the library -In the initialization snippet, set an environment name, service name, and version number. In the examples below, `app-name` specifies the variant of the application that generates data. +In the initialization snippet, set an environment name, service name, and client token. + +The SDK should be initialized as early as possible in the app lifecycle, specifically in the `AppDelegate`. This ensures all measurements, including application startup duration, are captured correctly. For apps built with SwiftUI, you can use `@UIApplicationDelegateAdaptor` to hook into the `AppDelegate`. + +
Initializing the SDK elsewhere (e.g., later during view loading) may result in inaccurate or missing telemetry, especially around app startup performance.
For more information, see [Using Tags][5]. @@ -402,8 +406,8 @@ For example, if the current tracking consent is `.pending`: ### Step 4 - Start sending data -#### Initialize the Datadog Monitor -Configure and register the Datadog Monitor. You only need to do it once, usually in your `AppDelegate` code: +#### Enable RUM +Configure and start RUM. This should be done once and as early as possible, specifically in your `AppDelegate`: {{< tabs >}} {{% tab "Swift" %}} From 3e2f0eaf7a2464b694f3593812880a8e3deaa530 Mon Sep 17 00:00:00 2001 From: Maciek Grzybowski Date: Fri, 18 Jul 2025 12:38:05 +0200 Subject: [PATCH 2/4] Clarify SDK and RUM initialization timing requirements in docs --- .../real_user_monitoring/mobile_and_tv_monitoring/ios/setup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/real_user_monitoring/mobile_and_tv_monitoring/ios/setup.md b/content/en/real_user_monitoring/mobile_and_tv_monitoring/ios/setup.md index 4c36c7680f6eb..1da376da839e4 100644 --- a/content/en/real_user_monitoring/mobile_and_tv_monitoring/ios/setup.md +++ b/content/en/real_user_monitoring/mobile_and_tv_monitoring/ios/setup.md @@ -133,7 +133,7 @@ For more information about setting up a client token, see the [Client token docu In the initialization snippet, set an environment name, service name, and client token. -The SDK should be initialized as early as possible in the app lifecycle, specifically in the `AppDelegate`. This ensures all measurements, including application startup duration, are captured correctly. For apps built with SwiftUI, you can use `@UIApplicationDelegateAdaptor` to hook into the `AppDelegate`. +The SDK should be initialized as early as possible in the app lifecycle, specifically in the `AppDelegate`'s `application(_:didFinishLaunchingWithOptions:)` callback. This ensures all measurements, including application startup duration, are captured correctly. For apps built with SwiftUI, you can use `@UIApplicationDelegateAdaptor` to hook into the `AppDelegate`.
Initializing the SDK elsewhere (e.g., later during view loading) may result in inaccurate or missing telemetry, especially around app startup performance.
From 648503287400cd53894e367772c20119342db5fc Mon Sep 17 00:00:00 2001 From: Maciek Grzybowski Date: Fri, 18 Jul 2025 12:41:36 +0200 Subject: [PATCH 3/4] Change "e.g." to "for example" --- .../real_user_monitoring/mobile_and_tv_monitoring/ios/setup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/real_user_monitoring/mobile_and_tv_monitoring/ios/setup.md b/content/en/real_user_monitoring/mobile_and_tv_monitoring/ios/setup.md index 1da376da839e4..f94329f3d18e6 100644 --- a/content/en/real_user_monitoring/mobile_and_tv_monitoring/ios/setup.md +++ b/content/en/real_user_monitoring/mobile_and_tv_monitoring/ios/setup.md @@ -135,7 +135,7 @@ In the initialization snippet, set an environment name, service name, and client The SDK should be initialized as early as possible in the app lifecycle, specifically in the `AppDelegate`'s `application(_:didFinishLaunchingWithOptions:)` callback. This ensures all measurements, including application startup duration, are captured correctly. For apps built with SwiftUI, you can use `@UIApplicationDelegateAdaptor` to hook into the `AppDelegate`. -
Initializing the SDK elsewhere (e.g., later during view loading) may result in inaccurate or missing telemetry, especially around app startup performance.
+
Initializing the SDK elsewhere (for example later during view loading) may result in inaccurate or missing telemetry, especially around app startup performance.
For more information, see [Using Tags][5]. From cb9018479800e499e7145602cef4222167f3e771 Mon Sep 17 00:00:00 2001 From: Maciek Grzybowski Date: Fri, 18 Jul 2025 12:49:49 +0200 Subject: [PATCH 4/4] Use single space --- .../real_user_monitoring/mobile_and_tv_monitoring/ios/setup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/real_user_monitoring/mobile_and_tv_monitoring/ios/setup.md b/content/en/real_user_monitoring/mobile_and_tv_monitoring/ios/setup.md index f94329f3d18e6..5d80226b6606a 100644 --- a/content/en/real_user_monitoring/mobile_and_tv_monitoring/ios/setup.md +++ b/content/en/real_user_monitoring/mobile_and_tv_monitoring/ios/setup.md @@ -133,7 +133,7 @@ For more information about setting up a client token, see the [Client token docu In the initialization snippet, set an environment name, service name, and client token. -The SDK should be initialized as early as possible in the app lifecycle, specifically in the `AppDelegate`'s `application(_:didFinishLaunchingWithOptions:)` callback. This ensures all measurements, including application startup duration, are captured correctly. For apps built with SwiftUI, you can use `@UIApplicationDelegateAdaptor` to hook into the `AppDelegate`. +The SDK should be initialized as early as possible in the app lifecycle, specifically in the `AppDelegate`'s `application(_:didFinishLaunchingWithOptions:)` callback. This ensures all measurements, including application startup duration, are captured correctly. For apps built with SwiftUI, you can use `@UIApplicationDelegateAdaptor` to hook into the `AppDelegate`.
Initializing the SDK elsewhere (for example later during view loading) may result in inaccurate or missing telemetry, especially around app startup performance.