fix: Use relative links (#6699)

Absolute links break the dev environment

Author: evanpurkhiser

src/api/auth.mdx

@@ -19,7 +19,7 @@ If your authentication token is `1a2b3c`, then the command should be:
 curl -H 'Authorization: Bearer 1a2b3c' https://sentry.io/api/0/projects/
 ```
 
-You can create authentication tokens within Sentry by [creating an internal integration](https://docs.sentry.io/product/integrations/integration-platform/#internal-integrations). This is also available for self-hosted Sentry.
+You can create authentication tokens within Sentry by [creating an internal integration](/product/integrations/integration-platform/#internal-integrations). This is also available for self-hosted Sentry.
 
 ### User authentication tokens
 

src/docs/product/accounts/pricing.mdx

@@ -30,8 +30,8 @@ If you run out of **both** your prepaid and on-demand volume, any new data you s
 
 On May 1st, Sentry will move to unit-based Performance pricing. This means customers will be charged based on a volume of total units for two different Performance event types:
 
-- **Transactions** - Consumes 1 Performance Unit and sent by projects with only [Tracing](https://docs.sentry.io/product/sentry-basics/tracing/) enabled.
-- **Transactions with Profiling** - Consumes 1.3 Performance Units and sent by projects that also have [Profiling](https://docs.sentry.io/product/profiling/) enabled.
+- **Transactions** - Consumes 1 Performance Unit and sent by projects with only [Tracing](/product/sentry-basics/tracing/) enabled.
+- **Transactions with Profiling** - Consumes 1.3 Performance Units and sent by projects that also have [Profiling](/product/profiling/) enabled.
 
 While **your current subscription volume won't change,** your current transactions quota will be converted to Performance Units at a 1:1 ratio. Depending on the Performance event types sent to Sentry, the rate at which you consume your total quota may change.
 

src/docs/product/accounts/sso/index.mdx

@@ -157,7 +157,7 @@ In your Jumploud Admin portal:
 1. Navigate to **User Authentication > SSO**.
 1. Add a new SSO application and search for Sentry.
 1. Click "Configure".
-1. Under the SSO menu, update the SP Entity ID and ACS URLs for your tenant. They should be in the format as described [here](https://docs.sentry.io/product/accounts/sso/saml2/#register-sentry-with-idp).
+1. Under the SSO menu, update the SP Entity ID and ACS URLs for your tenant. They should be in the format as described [here](/product/accounts/sso/saml2/#register-sentry-with-idp).
 1. Click "save".
 
 Be sure that you have assigned yourself to the Sentry app in Jumpcloud before attempting these next steps.

src/docs/product/accounts/sso/saml2.mdx

@@ -120,7 +120,7 @@ Because Sentry uses Just-In-Time (JIT) provisioning, new members are registered
 
 ## SCIM Provisioning
 
-SCIM is available for automatic user provisioning, deprovisioning, and team assignment for SAML2 IdPs. [Configure Sentry for SCIM](https://docs.sentry.io/product/accounts/sso/okta-sso/okta-scim/#sentry-configuration), and then follow your IdP's documentation for further setup. Learn more about the Sentry SCIM API endpoints in the [SCIM API documentation](https://docs.sentry.io/api/scim/).
+SCIM is available for automatic user provisioning, deprovisioning, and team assignment for SAML2 IdPs. [Configure Sentry for SCIM](/product/accounts/sso/okta-sso/okta-scim/#sentry-configuration), and then follow your IdP's documentation for further setup. Learn more about the Sentry SCIM API endpoints in the [SCIM API documentation](/api/scim/).
 
 ## FAQ
 

src/docs/product/cli/send-event.mdx

@@ -102,4 +102,4 @@ eval "$(sentry-cli bash-hook)"
 # rest of the script goes here
 ```
 
-Alternatively you can use other mechanisms like [a `.sentryclirc` file](https://docs.sentry.io/product/cli/configuration/#configuration-file) to configure the DSN.
+Alternatively you can use other mechanisms like [a `.sentryclirc` file](/product/cli/configuration/#configuration-file) to configure the DSN.

src/docs/product/integrations/troubleshooting.mdx

@@ -9,7 +9,7 @@ Sentry integrates with many third party services to make your development experi
 ## If you've changed your organization slug
 
 - Any integration that creates links directly to Sentry issues will continue creating correct links going forward, **but existing links will no longer work as expected**. This includes, for example, Slack notifications containing links to Sentry alerts, and Jira tickets that link to Sentry issues.
-- Most [deployment integrations](https://docs.sentry.io/product/integrations/#deployment) use [Sentry CLI](https://github.com/getsentry/sentry-cli) under the hood, which requires providing your organization slug by way of the `SENTRY_ORG` environment variable. For these integrations to continue working, **you must manually update this variable on the appropriate service**.
+- Most [deployment integrations](/product/integrations/#deployment) use [Sentry CLI](https://github.com/getsentry/sentry-cli) under the hood, which requires providing your organization slug by way of the `SENTRY_ORG` environment variable. For these integrations to continue working, **you must manually update this variable on the appropriate service**.
 - If you're using any of the following integrations, you need to manually update the organization slug to maintain functionality:
 
   - [Bitbucket Pipelines](/product/releases/setup/release-automation/bitbucket-pipelines/)

src/docs/product/relay/pii-and-data-scrubbing.mdx

@@ -87,6 +87,6 @@ For example:
 }
 ```
 
-[advanced data scrubbing]: https://docs.sentry.io/platform-redirect/?next=/data-management/advanced-datascrubbing/
+[advanced data scrubbing]: /platform-redirect/?next=/data-management/advanced-datascrubbing/
 [relay]: https://github.com/getsentry/relay
 [piinguin]: https://getsentry.github.io/piinguin

src/docs/product/session-replay/protecting-user-privacy.mdx

@@ -10,7 +10,7 @@ With the extra scrutiny and sensitivity around session replay products and the l
 
 Sentry's Session Replay is not an actual “screen” recording, but instead a recording of changes in the web browsers' Document Object Model (DOM) (i.e., the data representation of the page). This important distinction means that the data captured by Session Replay can be searched and stripped.
 
-We provide our customers with a range of [configuration options](/platforms/javascript/session-replay/privacy/) to control how much (or how little) data is collected. Customers can use our privacy controls to help ensure no sensitive user data leaves the browser. Customers can also use [server-side scrubbing](https://docs.sentry.io/product/data-management-settings/scrubbing/server-side-scrubbing/) capabilities to further filter and remove sensitive user data, or our deletion capabilities to delete individual recordings after ingestion.
+We provide our customers with a range of [configuration options](/platforms/javascript/session-replay/privacy/) to control how much (or how little) data is collected. Customers can use our privacy controls to help ensure no sensitive user data leaves the browser. Customers can also use [server-side scrubbing](/product/data-management-settings/scrubbing/server-side-scrubbing/) capabilities to further filter and remove sensitive user data, or our deletion capabilities to delete individual recordings after ingestion.
 
 Below we expand on what data is potentially collected, how they are treated by default, and what additional controls are available to customers. At the bottom of this page you'll also find our [Legal & Privacy FAQ](#legal-and-privacy-faq).
 
@@ -62,4 +62,4 @@ See our [subprocessor list](https://sentry.io/legal/subprocessors/) for our infr
 
 **Q: How long do you retain Session Replay data?**
 
-Please see [our security policy](https://sentry.io/security/).  Our data retention policy applies to the overall Sentry service, including Session Replay.
+Please see [our security policy](https://sentry.io/security/). Our data retention policy applies to the overall Sentry service, including Session Replay.

src/includes/beta-note-opentelemetry.mdx

@@ -4,11 +4,11 @@ OpenTelemetry Support is now generally availabile. If you have any questions or
 
 Currently, OpenTelemetry is supported on the following SDKs:
 
-- [NodeJS](https://docs.sentry.io/platforms/node/performance/instrumentation/opentelemetry/)
-- [NextJS](https://docs.sentry.io/platforms/javascript/guides/nextjs/performance/instrumentation/opentelemetry/)
-- [Python](https://docs.sentry.io/platforms/python/performance/instrumentation/opentelemetry/)
-- [Ruby](https://docs.sentry.io/platforms/ruby/performance/instrumentation/opentelemetry/)
-- [Java](https://docs.sentry.io/platforms/java/performance/instrumentation/opentelemetry/)
-- [Go](https://docs.sentry.io/platforms/go/performance/instrumentation/opentelemetry/)
+- [NodeJS](/platforms/node/performance/instrumentation/opentelemetry/)
+- [NextJS](/platforms/javascript/guides/nextjs/performance/instrumentation/opentelemetry/)
+- [Python](/platforms/python/performance/instrumentation/opentelemetry/)
+- [Ruby](/platforms/ruby/performance/instrumentation/opentelemetry/)
+- [Java](/platforms/java/performance/instrumentation/opentelemetry/)
+- [Go](/platforms/go/performance/instrumentation/opentelemetry/)
 
 </Note>

src/platform-includes/getting-started-config/apple.mdx

@@ -51,7 +51,7 @@ struct SwiftUIApp: App {
 
 ## Experimental features
 
-> Want to play with some new features? Try out our experimental features for [file I/O](/platforms/apple/performance/instrumentation/automatic-instrumentation/#file-io-instrumentation), [Core Data](/platforms/apple/performance/instrumentation/automatic-instrumentation/#core-data-instrumentation), [User Interaction Instrumentation](/platforms/apple/performance/instrumentation/automatic-instrumentation/#user-interaction-instrumentation), [Screenshots](https://docs.sentry.io/platforms/apple/guides/ios/enriching-events/screenshots/). Experimental features are still a work-in-progress and may have bugs. We recognize the irony.
+> Want to play with some new features? Try out our experimental features for [file I/O](/platforms/apple/performance/instrumentation/automatic-instrumentation/#file-io-instrumentation), [Core Data](/platforms/apple/performance/instrumentation/automatic-instrumentation/#core-data-instrumentation), [User Interaction Instrumentation](/platforms/apple/performance/instrumentation/automatic-instrumentation/#user-interaction-instrumentation), [Screenshots](/platforms/apple/guides/ios/enriching-events/screenshots/). Experimental features are still a work-in-progress and may have bugs. We recognize the irony.
 >
 > Let us know if you have feedback through [GitHub issues](https://github.com/getsentry/sentry-cocoa/issues).
 

src/platform-includes/getting-started-primer/apple.mdx

@@ -25,7 +25,7 @@
   - Rendering of UIViewControllers
   - Performance of HTTP requests
   - Distributed tracing
-  - [Mobile Vitals](https://docs.sentry.io/product/performance/mobile-vitals/)
+  - [Mobile Vitals](/product/performance/mobile-vitals/)
     - Cold and warm start
     - Slow and frozen frames
   - Performance of <PlatformLink to="/performance/instrumentation/automatic-instrumentation/#file-io-tracing">file I/O</PlatformLink> operations

src/platform-includes/getting-started-primer/javascript.nextjs.mdx

@@ -13,7 +13,7 @@ Features:
 - [Breadcrumbs](/platforms/javascript/enriching-events/breadcrumbs/) created for outgoing HTTP request with XHR and Fetch, and console logs
 - [Release health](/product/releases/health/) for tracking crash-free users and sessions
 - Automatic [Performance Monitoring](/product/performance/) for both the client and server, from version `6.5.0`
-- Errors and Performance support for [Middleware](https://vercel.com/docs/concepts/functions/edge-middleware) and [Edge routes](https://vercel.com/docs/concepts/functions/edge-functions) in Vercel's edge runtime. Due to complexities with the runtime, some features of errors like stacktraces may not not be as expected. Requires <code>sentry.edge.config.js</code>, more info [here](https://docs.sentry.io/platforms/javascript/guides/nextjs/manual-setup/#create-initialization-config-files)
+- Errors and Performance support for [Middleware](https://vercel.com/docs/concepts/functions/edge-middleware) and [Edge routes](https://vercel.com/docs/concepts/functions/edge-functions) in Vercel's edge runtime. Due to complexities with the runtime, some features of errors like stacktraces may not not be as expected. Requires <code>sentry.edge.config.js</code>, more info [here](/platforms/javascript/guides/nextjs/manual-setup/#create-initialization-config-files)
 
 Under the hood the SDK relies on our [React SDK](/platforms/javascript/guides/react/) on the frontend and [Node SDK](/platforms/node) on the backend, which makes all features available in those SDKs also available in this SDK.
 Using a [custom server](https://nextjs.org/docs/advanced-features/custom-server) is currently not supported.

src/platform-includes/getting-started-primer/note/apple.mdx

@@ -1,6 +1,6 @@
 <Note>
 
-Sentry's SDKs report an error automatically whenever a thrown error or exception goes uncaught in your application, causing the application to crash. The SDK automatically hooks into all signal and exception handlers, except for macOS, where a simple [manual setup](https://docs.sentry.io/platforms/apple/guides/macos/usage/#capturing-uncaught-exceptions-in-macos) is required for uncaught exceptions.
+Sentry's SDKs report an error automatically whenever a thrown error or exception goes uncaught in your application, causing the application to crash. The SDK automatically hooks into all signal and exception handlers, except for macOS, where a simple [manual setup](/platforms/apple/guides/macos/usage/#capturing-uncaught-exceptions-in-macos) is required for uncaught exceptions.
 
 The SDK builds a crash report that persists to disk and tries to send the report right after the crash. Since the environment may be unstable at the crash time, the report is guaranteed to send once the application is started again.
 

src/platform-includes/session-replay/pre-requisites/javascript.capacitor.mdx

@@ -1,4 +1,4 @@
 For the sentry-replay integration to work, you must have the [Sentry Electron SDK package](https://www.npmjs.com/package/@sentry/electron) installed. The minimum version required for the SDK is `4.2.0`.
 If you're on an older version of the SDK, please check the [troubleshooting
 document to help on
-migration](https://docs.sentry.io/platforms/javascript/guides/electron/troubleshooting/).
+migration](/platforms/javascript/guides/electron/troubleshooting/).

src/platform-includes/sourcemaps/upload/cli/javascript.mdx

@@ -4,7 +4,7 @@ In this guide, you'll learn how to successfully upload source maps using our `se
 
 You can use two methods of uploading source maps:
 1. Artifact Bundles (Preferred): Upload source maps whenever you need
-2. Release Bundles: Upload source maps when you create a new [Sentry release](https://docs.sentry.io/product/releases/)
+2. Release Bundles: Upload source maps when you create a new [Sentry release](/product/releases/)
 
 ## Configure Sentry CLI
 
@@ -27,7 +27,7 @@ export SENTRY_PROJECT=___PROJECT_SLUG___
 
 <Note>
 
-You can find installation instructions for `sentry-cli` here: https://docs.sentry.io/product/cli/installation/
+You can find installation instructions for `sentry-cli` here: /product/cli/installation/
 
 For more info on `sentry-cli` configuration visit the [Sentry CLI configuration docs](/product/cli/configuration/).
 

src/platforms/common/enriching-events/identify-user.mdx

@@ -67,7 +67,7 @@ The user segment, for apps that divide users in user segments.
 ### `ip_address`
 
 The user's IP address. If the user is unauthenticated, Sentry uses the IP address as a unique identifier for the user.
-Serverside SDKs that instrument incoming requests will attempt to pull the IP address from the HTTP request data (`request.env.REMOTE_ADDR` field in JSON), if available. <PlatformSection notSupported={["javascript", "node"]}>That might require <PlatformIdentifier name="send-default-pii" /> set to `true` in the SDK options.</PlatformSection><PlatformSection supported={["javascript", "node"]}>This requires you to set the `include.ip` option to `true` in the [`RequestData`](https://docs.sentry.io/platforms/node/guides/connect/configuration/integrations/default-integrations/#requestdata) integration.</PlatformSection>
+Serverside SDKs that instrument incoming requests will attempt to pull the IP address from the HTTP request data (`request.env.REMOTE_ADDR` field in JSON), if available. <PlatformSection notSupported={["javascript", "node"]}>That might require <PlatformIdentifier name="send-default-pii" /> set to `true` in the SDK options.</PlatformSection><PlatformSection supported={["javascript", "node"]}>This requires you to set the `include.ip` option to `true` in the [`RequestData`](/platforms/node/guides/connect/configuration/integrations/default-integrations/#requestdata) integration.</PlatformSection>
 
 If the user's `ip_address` is set to `"{{auto}}"`, Sentry will infer the IP address from the connection between your app and Sentry's server. <PlatformSection supported={["apple"]}>Due to backward compatibility concerns, Sentry sets the IP address to `"{{auto}}"` out of the box for Apple. Therefore setting <PlatformIdentifier name="send-default-pii" /> to `false` won't stop Sentry from collecting users' IP addresses via the client connection. Read the paragraphs below to find out how to opt out of collecting users' IP addresses.</PlatformSection>
 

src/platforms/python/common/data-collected.mdx

@@ -56,7 +56,7 @@ The request body of incoming HTTP requests can be sent to Sentry. Whether it's s
     -JSON and form bodies are sent
      -Raw request bodies are always removed
      -Uploaded files in the request bodies are never sent to Sentry
-- **The size of the request body:** There's a ["request_bodies"](https://docs.sentry.io/platforms/python/configuration/options/#request-bodies) option that's set to `medium` by default. This means that larger request bodies aren't sent to Sentry.
+- **The size of the request body:** There's a ["request_bodies"](/platforms/python/configuration/options/#request-bodies) option that's set to `medium` by default. This means that larger request bodies aren't sent to Sentry.
 
 If you want to prevent bodies from being sent to Sentry altogether, set `request_bodies` to `"never"`.
 

src/platforms/unity/configuration/il2cpp.mdx

@@ -16,7 +16,7 @@ The Sentry SDK provides line number support for IL2CPP builds for the following
 - Android
 - iOS
 
-When you build with IL2CPP, errors in your game will happen in the native code. Also, the mapping between your C# code and the generated C++ code is part of the build process and isn't shipped with your game. That means the event the Sentry SDK reports can only contain the native stack trace. To provide you with C# line numbers, the Sentry server needs to have access to that line mapping through [Debug Information Files](https://docs.sentry.io/platforms/unity/data-management/debug-files/).
+When you build with IL2CPP, errors in your game will happen in the native code. Also, the mapping between your C# code and the generated C++ code is part of the build process and isn't shipped with your game. That means the event the Sentry SDK reports can only contain the native stack trace. To provide you with C# line numbers, the Sentry server needs to have access to that line mapping through [Debug Information Files](/platforms/unity/data-management/debug-files/).
 
 This feature is enabled by default. You can opt out of it through the editor configuration window by selecting **Tools -> Sentry -> Advanced -> IL2CPP line numbers** or [programmatically](/platforms/unity/configuration/options/#programmatic-configuration).