Description
The Mobile Vitals dashboard currently hard-filters on transaction.op:[ui.load,navigation], which means standalone app start transactions using app.start.cold / app.start.warm ops won't appear in the dashboard.
The dashboard queries need to be updated to also include app.start.* ops so customers can see their app start performance data in Mobile Vitals after adopting standalone app start transactions.
Context
- See detailed analysis on the Cocoa issue
- Standalone app start transactions (JAVA-283) introduce new ops:
app.start.cold and app.start.warm
- Without this change, customers who enable standalone app start will lose visibility in Mobile Vitals
Scope
- Update Mobile Vitals queries to include
app.start.cold and app.start.warm transaction ops
- Verify that app start metrics (TTID, TTFD,
app_start_cold, app_start_warm measurements) render correctly in the dashboard
- Ensure backwards compatibility — existing
ui.load transactions with attached app start data should continue to work
Description
The Mobile Vitals dashboard currently hard-filters on
transaction.op:[ui.load,navigation], which means standalone app start transactions usingapp.start.cold/app.start.warmops won't appear in the dashboard.The dashboard queries need to be updated to also include
app.start.*ops so customers can see their app start performance data in Mobile Vitals after adopting standalone app start transactions.Context
app.start.coldandapp.start.warmScope
app.start.coldandapp.start.warmtransaction opsapp_start_cold,app_start_warmmeasurements) render correctly in the dashboardui.loadtransactions with attached app start data should continue to work