change: [M3-10534] - Error in Sentry: window.crypto.randomUUID is not a function

[bill-akamai]

Description 📝

This PR addresses false positive errors in Sentry: "window.crypto.randomUUID is not a function." These are believed to be caused by synthetic monitoring tools like Catchpoint which lack full DOM API support including the crypto API.

Changes 🔄

• Added condition to ignore error if user agent contains "Catchpoint" in initSentry.ts

Scope 🚢

• All customers
• Some customers (e.g. in Beta or Limited Availability)
• No customers / Not applicable

Reproduction steps

"window.crypto.randomUUID is not a function" errors can be observed in our Sentry dashboard. In the "Context" section of these reports, the browser listed is "Catchpoint," a synthetic monitoring tool which does not have access to the DOM APIs like window.crypto.

Verification steps

• Confirm test passes: pnpm test packages/manager/src/initSentry.test.ts

Post deployment verification will include monitoring Sentry logs for reduction in crypto API false positives.

Author Checklists

As an Author, to speed up the review process, I considered 🤔

👀 Doing a self review
❔ Our contribution guidelines
🤏 Splitting feature into small PRs
➕ Adding a changeset
🧪 Providing/improving test coverage
🔐 Removing all sensitive information from the code and PR description
🚩 Using a feature flag to protect the release
👣 Providing comprehensive reproduction steps
📑 Providing or updating our documentation
🕛 Scheduling a pair reviewing session
📱 Providing mobile support
♿ Providing accessibility support

• I have read and considered all applicable items listed above.

As an Author, before moving this PR from Draft to Open, I confirmed ✅

• All tests and CI checks are passing
• TypeScript compilation succeeded without errors
• Code passes all linting rules

[bnussman-akamai]

What do you think about, rather than changing up any auth logic, we just ignore any errors from catchpoint user-agents.

I do like the idea of decreasing Sentry noise, but I think there is value in letting normal user browsers still throw so we have an insights into browsers and users can't use Cloud Manager due to a lack of the crypto API

[bill-akamai]

I do like the idea of decreasing Sentry noise, but I think there is value in letting normal user browsers still throw so we have an insights into browsers and users can't use Cloud Manager due to a lack of the crypto API

Thanks @bnussman-akamai I was thinking this would be the preferred method but didn't even know we had this file. Updated the PR.

[bnussman-akamai]

Looks good.

Just left a comment about avoiding anys

[mjac0bs]

Change makes sense and test is passing, thank you. Banks' suggestion is a good one.

[linode-gh-bot]

Cloud Manager UI test results

🎉 745 passing tests on test run #9 ↗︎

❌ Failing	✅ Passing	↪️ Skipped	🕐 Duration
0 Failing	745 Passing	6 Skipped	35m 18s