You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/platforms/flutter/integrations/app-start-instrumentation.mdx
+9-8Lines changed: 9 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,15 +20,16 @@ App start instrumentation is available on **iOS** and **Android**.
20
20
21
21
Before diving into the configuration, it's important to understand how app start instrumentation behaves:
22
22
23
-
- It tracks the length of time from the **earliest native process initialization** until the very first frame rendered that is reported by [addTimingsCallback](https://api.flutter.dev/flutter/scheduler/SchedulerBinding/addTimingsCallback.html). Once the app start is processed, the SDK removes the callback in order to avoid additional overhead.
24
-
- After receiving information about the start and end times of the app launch, the SDK does the following:
25
-
- creates a transaction with the name `ui.load`
26
-
- in the transaction attaches a span with the operation `app.start.cold` or `app.start.warm`
27
-
- attaches the app start metrics to the transaction
23
+
App start instrumentation tracks the duration between the earliest native process initialization and the first frame rendered (as reported by [addTimingsCallback](https://api.flutter.dev/flutter/scheduler/SchedulerBinding/addTimingsCallback.html)). Once the app start is processed, we remove the callback to avoid additional overhead.
24
+
25
+
When the SDK receives the start and end times of the app launch, we:
26
+
- Create a transaction named `ui.load`
27
+
- Attach a span with either `app.start.cold` or `app.start.warm` operation
28
+
- Add app start metrics to the transaction
28
29
29
30
<Note>
30
31
31
-
The SDK differentiates between a cold and a warm start, but doesn't track hot starts/resumes.
32
+
While we differentiate between cold and warm starts, we don't track hot starts/resumes.
32
33
33
34
</Note>
34
35
@@ -45,13 +46,13 @@ This instrumentation is automatically enabled. There is no need for further conf
45
46
46
47
## Verify
47
48
48
-
### 1. Launch your app:
49
+
### 1. Launch Your App:
49
50
50
51
Launch your Sentry configured app.
51
52
52
53
### 2. Locate Your Transaction:
53
54
54
-
Open the [sentry.io](https://sentry.io/) performance dashboard, find, and select the 'root /' transaction.
55
+
Open the [sentry.io](https://sentry.io/) performance dashboard, find, and select the 'root /' transaction and navigate to the trace view of a sampled event.
0 commit comments