[Onboarding and Invitation Flow] Onboarding Flow Is Too Brittle

### Environment SaaS ([https://sentry.io/](<https://sentry.io/>)) ### Steps to Reproduce When you receive an invitation to join a Sentry organization the invitation contains two calls-to-action:  1. Join Your Team 2. Check out the [Sentry website](<https://sentry.io/>) ### Expected Result If you select to check out the Sentry website - the context of visiting this page from an invitation should be maintained. That way you can click the getting started button and be taken to the Invitation Flow. ### Actual Result Once you opt to check out Sentry first, your only option from this view is to create a new organization. Which creates a poor user experience on first join. ### Brainstorming Consider adding some query params to the second call to action that will redirect the user to the invitation when clicking Getting Started instead of [https://sentry.io/signup/](<https://sentry.io/signup/>) ### Product Area Sign In ### Link *No response* ### DSN *No response* ### Version *No response* We want to define a set of [lightweight metrics](<https://docs.sentry.io/product/explore/metrics/>) that SDKs can automatically collect for e.g. framework, language or platform, focusing only on signals that **do NOT overlap with Tracing**. Ideally these metrics should give a quick sense of app or runtime health, … while deeper investigation will still rely on traces or profiles.<br><br>Examples**:** * Node.js runtime metrics (e.g., event loop delay, heap usage) * Prisma-related metrics in Next.js * Mobile CPU / memory usage to help surface potential …