Sentry: Turn on auto instrument server funcs

[masonmcelvain]

I'm not sure why this was turned off, and it doesn't seem to make any difference with it on, but let's turn it back on.

https://docs.sentry.io/platforms/javascript/guides/nextjs/manual-setup/#configure-server-side-auto-instrumentation

automatically instrument API routes and server-side Next.js data fetching methods with error and performance monitoring.

qa_req 0

CC @danielbeardsley

Connects #1491

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
react-commerce	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 11, 2023 8:37pm
react-commerce-prod	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 11, 2023 8:37pm

[github-actions]

📦 Next.js Bundle Analysis for @ifixit/commerce-frontend

This analysis was generated by the Next.js Bundle Analysis action. 🤖

This PR introduced no changes to the JavaScript bundle! 🙌

[github-actions]

📦 Next.js Bundle Analysis for @ifixit/commerce-frontend

This analysis was generated by the Next.js Bundle Analysis action. 🤖

This PR introduced no changes to the JavaScript bundle! 🙌

[danielbeardsley]

CR 👍

I think this is the right thing, but it's hard for me to believe we aren't instrumenting with sentry at all except for the places where we do it explicitly.

deploy_block 👍 on looking at those explicit places and ensuring we won't be double-reporting.

[github-actions]

📦 Next.js Bundle Analysis for @ifixit/commerce-frontend

This analysis was generated by the Next.js Bundle Analysis action. 🤖

This PR introduced no changes to the JavaScript bundle! 🙌

[masonmcelvain]

Great suggestion! I did a quick audit of the places we explicitly use sentry, and I think these were the only potential double-captures. Our applySentryFetchMiddleware() middleware doesn't look like it will double report.

un_deploy_block ✌🏻

[danielbeardsley]

CR 👍

Nice work!