Problem
When analyzing expense creation performance in Sentry, all expense flows (request money, distance, split, track, invoice) are mixed under one broad span. This makes it hard to identify which specific flow has performance issues and to measure the full round-trip including server response time.
Solution
Add granular Sentry spans to the expense creation flow:
- Add
ManualSubmitExpense span measuring confirm tap → API dispatch, tagged with scenario attribute (e.g. request_money_manual, distance, split, track_expense, invoice) to distinguish flows
- Add
ManualNavigateAfterExpenseCreate span measuring post-submit navigation to the Search page
- Add
SentryServerTiming middleware that creates a ManualExpenseServerResponse span for expense write commands
PR: #82287
Problem
When analyzing expense creation performance in Sentry, all expense flows (request money, distance, split, track, invoice) are mixed under one broad span. This makes it hard to identify which specific flow has performance issues and to measure the full round-trip including server response time.
Solution
Add granular Sentry spans to the expense creation flow:
ManualSubmitExpensespan measuring confirm tap → API dispatch, tagged with scenario attribute (e.g. request_money_manual, distance, split, track_expense, invoice) to distinguish flowsManualNavigateAfterExpenseCreatespan measuring post-submit navigation to the Search pageSentryServerTimingmiddleware that creates aManualExpenseServerResponsespan for expense write commandsPR: #82287