Application Performance Management Plus
Application Performance Management Plus
Document
- Documentation
Application Performance Management PlusUser guideClient monitoringApp monitoringFAQiOS-side monitoringWhy is some startup time data unusually large, reaching tens, hundreds, or even thousands?
Copy page
Download PDFiOS-side monitoring
Why is some startup time data unusually large, reaching tens, hundreds, or even thousands?
Copy pageDownload PDFWhy is some startup time data unusually large, reaching tens, hundreds, or even thousands?
- This data is real data collected by APMInsight, but it does not match the usage habits of most users. It is a type of abnormal data and is not very helpful for problem analysis. It is a kind of "pollution" for the dashboard data, and you can configure it to be filtered out in the custom settings:
- Why is this kind of data generated?
- Startup monitoring collects the data of the following stages during app startup:
- If the user switches the app to the background before these four stages are completed and then starts it again after a long time, two situations will occur: If the iPhone terminates the app process, then the next startup by the user is a new startup, and the previous incomplete startup no longer exists, and APMInsight will not report the previous startup. If the iPhone does not terminate the process, the app continues the previous incomplete startup, and after the startup completes, APMInsight reports the time of this startup, resulting in an unusually long startup time.
- How to determine whether abnormal startup data is caused by the reasons described above? You can determine this by analyzing user behavior together with other types of logs.
- On the error statistics and tracking page, find an abnormal startup record and copy the DeviceID.
- In single-point tracing, search for the user's log information by the DeviceID and obtain two timestamps from the raw information in the startup log. APMInsight calculates the app startup time based on these two timestamps, and then checks whether no new logs were generated for a long period between these two time points.
-
- As shown in the figure below, there are several network logs at 7:38, after which no logs are generated. 7:38 is exactly the first time point recorded in the startup log, and no new logs appear until 17:46. 17:46 is the last time point recorded in the startup log, so the final calculated startup time will be very large.
Last updated: 2026.10.23 11:17:22
All rights reserved © Beijing Volcano Engine Technology Co., Ltd2024
