Action Performed:
- When the app starts we measure the time it takes until the
SidebarLinks are rendered, known as "App start TTI".
This measurement is reported to Grafana. Currently any waiting time due to waiting on network data is included in the TTI. This PR changes that, and will only report the TTI when we render the SidebarLinks with cached data on the first render.
- Currently when reporting to grafana no information about the environment is included, meaning data from staging and production is mixed. This PR also adds env info to the grafana logging.
This is an effort towards: #11997
Expected Result:
- Only report TTI from cached render results (we want to know if we introduced performance regression issues in the code, not whether the API is slow to respond)
- Events reported to grafana include environment information
Actual Result:
/
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Yes they can, this is just for internal performance monitoring.
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.2.48-2
Reproducible in staging?: N/A
Reproducible in production?: N/A
Email or phone of affected tester (no customers): N/A
Logs: N/A
Notes/Photos/Videos: N/A
Expensify/Expensify Issue URL: N/A
Issue reported by: @hannojg
Slack conversation: None, but this issue #11997
View all open jobs on GitHub
Action Performed:
SidebarLinksare rendered, known as "App start TTI".This measurement is reported to Grafana. Currently any waiting time due to waiting on network data is included in the TTI. This PR changes that, and will only report the TTI when we render the
SidebarLinkswith cached data on the first render.This is an effort towards: #11997
Expected Result:
Actual Result:
/
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Yes they can, this is just for internal performance monitoring.
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.2.48-2
Reproducible in staging?: N/A
Reproducible in production?: N/A
Email or phone of affected tester (no customers): N/A
Logs: N/A
Notes/Photos/Videos: N/A
Expensify/Expensify Issue URL: N/A
Issue reported by: @hannojg
Slack conversation: None, but this issue #11997
View all open jobs on GitHub