[HOLD for payment 2024-08-07] [HOLD for payment 2024-08-05] Enable Firebase performance logging

[TMisiukiewicz]

Coming from https://expensify.slack.com/archives/C05LX9D6E07/p1721655178311639

Problem

Our current performance/reliability focus is on app behavior for specific accounts, but we are missing the broader view of performance trends over time for a wider audience. Additionally, CK cannot access Grafana dashboard, so we don't know how performance data behaves across the app for end users.

Solution

Let's enable capturing performance data in Firebase. This setup would automatically collect session data from a small number of users, including CPU and memory usage, network requests, etc. We could extend this by adding information about an account, such as the amount of personal details and reports on the account. This would allow us to link resource usage with the amount of data.

We could further enhance this by tracing screen rendering to gather information about slow rendering and frozen frames.

With all this data, we can identify and fix performance issues before they affect a significant portion of users, and prioritize features and fixes based on real user data.

Issue Owner

Current Issue Owner: @sakluger

[melvin-bot]

Triggered auto assignment to @sakluger (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[melvin-bot]

Reviewing label has been removed, please complete the "BugZero Checklist".

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.13-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• perf: enable capturing performance data in Firebase #46107

If no regressions arise, payment will be issued on 2024-08-05. 🎊

[melvin-bot]

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

• [@marcaaron] The PR that introduced the bug has been identified. Link to the PR:
• [@marcaaron] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
• [@marcaaron] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
• [@marcaaron] Determine if we should create a regression test for this bug.
• [@marcaaron] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
• [@sakluger] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:

[marcaaron]

This was new feature rather than a bug and no payments are needed here so gonna just close it out.

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.14-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• perf: attach accountID to Firebase Performance sessions #46284

If no regressions arise, payment will be issued on 2024-08-07. 🎊

[melvin-bot]

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

• [@marcaaron] The PR that introduced the bug has been identified. Link to the PR:
• [@marcaaron] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
• [@marcaaron] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
• [@marcaaron] Determine if we should create a regression test for this bug.
• [@marcaaron] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
• [@sakluger] Link the GH issue for creating/updating the regression test once above steps have been agreed upon: