feat: 1940 Add custom traces

[MarioAslau]

Description

This task is for adding custom spans to track activities that happen between app start and wallet UI load. The screenshot below is an example of a trace for Wallet UI load that takes about a minute to load. During that time, we can see a large gap between app start spans and the initial http requests.

The goal here is to isolate these areas and track them with custom spans. Once implemented, we can expect to see the custom spans appearing within the gap, which would inform us of the areas to optimize

Issue: https://github.com/MetaMask/mobile-planning/issues/1940

Technical Details

• Added custom span for when the Login screen is mounted to when the login button is tapped
• Added span for when the login button is tapped to when the wallet view is mounted
• Added custom span for Engine initialization process
• Added custom span for Store creation
• Added custom span Storage rehydration
• Added custom span fro Create New Wallet to Choose Password
• Added custom span for Biometrics authentication

Related issues

Fixes:

Manual testing steps

1. Go to this page...

Screenshots/Recordings

Before

After

Pre-merge author checklist

• I’ve followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• I've completed the PR template to the best of my ability
• I’ve included tests if applicable
• I’ve documented my code using JSDoc format if applicable
• I’ve applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

[github-actions]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[MarioAslau]

We are waiting to have a meeting with a Sentry representative to clarify some questions that we have, before merging this

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: c13b801
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/9d956e93-49cd-4658-91da-d5e2c9403e3e

Note

• You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: b1f17cb
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/5d53febd-7fa5-4764-b693-0e0367640f09

Note

• You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

[sethkfman]

LGTM

[github-actions]

Bitrise

🔄🔄🔄 pr_smoke_e2e_pipeline started on Bitrise...🔄🔄🔄

Commit hash: 2e8439b
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/cba7e6eb-6385-4324-af00-6364e1585ea4

Note

• This comment will auto-update when build completes
• You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 13f7674
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/f8f40593-e399-48a4-9c4c-32991421af4c

Note

• You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

[sonarqubecloud]

Quality Gate passed

Issues
2 New issues
0 Accepted issues

Measures
0 Security Hotspots
60.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[sethkfman]

LGTM

[EtherWizard33]

lgtm