Description

Setting a value for tracesSampleRate enables performance monitoring in Sentry. Once performance monitoring is enabled, transactions are sent to Sentry every time a user loads a page or navigates within the app. Since the amount of traffic the app gets is important, this means a lot of transactions are sent. By setting tracesSampleRate to a value lower than 1.0, we reduce the volume of transactions to a more reasonable amount.

Sentry documentation
Mobile implementation

Enabling Sentry performance monitoring will allow us to add app load time to our North Star metrics dashboards, like we do for Mobile.

Related issues

• None

Manual testing steps

1. Create your own Sentry instance

2. Go to Sentry Performance dashboard and you shall see no transaction

3. Select Settings in the sidebar menu, then select Projects in the secondary menu. Click your project then select Client Keys (DSN) from the secondary menu. Click the Configure button on the Client Keys page and copy your Project Id and Public Key.

4. Add/replace SENTRY_DSN_DEV variable in .metamaskrc

   SENTRY_DSN_DEV=https://{SENTRY_PUBLIC_KEY}@sentry.io/{SENTRY_PROJECT_ID}
   

5. Build the project to the ./dist/ folder with yarn dist

6. Add Extension to your browser

7. Open Extension and do some actions

8. Kill the Extension

9. Go to Sentry Performance dashboard and you shall see a few transactions

Screenshots/Recordings

Before

After

Pre-merge author checklist

• I’ve followed MetaMask Coding Standards.
• I've clearly explained what problem this PR is solving and how it is solved.
• I've linked related issues
• I've included manual testing steps
• I've included screenshots/recordings if applicable
• 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.
• I’ve properly set the pull request status:
  • In case it's not yet "ready for review", I've set it to "draft".
  • In case it's "ready for review", I've changed it from "draft" to "non-draft".

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.