fix: update broken external links across documentation (#15894)

vaind · claude · web-flow · commit fa70d049ef0a · 2026-01-02T23:08:20.000+01:00
## DESCRIBE YOUR PR Follow up from #15893 Updates various broken external links found by the link checker: - Fix Django REST Framework serializer docs URL - Update Sentry options.py path (master→main, correct directory) - Fix Transifex translation project URL - Replace deprecated Flux docs link with GitHub archive - Fix OpenTelemetry semantic conventions URLs - Update Mailgun documentation URL - Fix Ping Identity documentation URL - Update Flagsmith integration documentation URL - Fix Apple SDK troubleshooting Swift issue reference - Fix Xamarin SSL certificate issue reference - Update Remix meta function documentation links (v1→main) - Fix Next.js custom server documentation URL 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> ## IS YOUR CHANGE URGENT? Help us prioritize incoming PRs by letting us know when the change needs to go live. - [ ] Urgent deadline (GA date, etc.):  - [ ] Other deadline:  - [x] None: Not urgent, can wait up to 1 week+ ## SLA - Teamwork makes the dream work, so please add a reviewer to your PRs. - Please give the docs team up to 1 week to review your PR unless you've added an urgent due date to it. Thanks in advance for your help! ## PRE-MERGE CHECKLIST *Make sure you've checked the following before merging your changes:* - [ ] Checked Vercel preview for correctness, including links - [ ] PR was reviewed and approved by any necessary SMEs (subject matter experts) - [ ] PR was reviewed and approved by a member of the [Sentry docs team](https://github.com/orgs/getsentry/teams/docs) ## LEGAL BOILERPLATE  Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms. ## EXTRA RESOURCES - [Sentry Docs contributor guide](https://docs.sentry.io/contributing/) Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
diff --git a/develop-docs/backend/api/serializers.mdx b/develop-docs/backend/api/serializers.mdx
@@ -89,7 +89,7 @@ The serializer would return an error stating that the required field name was no
 
 Once you have verified that the data is valid, you can save the data in one of two ways. The example given above is the most commonly done in sentry. Taking the `serializer.object` which is simply the validated data (and will be `None` if `serializer.is_valid()` return `False`) and saving that data directly in the model with `<ModelName>.objects.create`.
 
-An alternative method uses more of Django Rest Framework's features, the [ModelSerializer](http://www.tomchristie.com/rest-framework-2-docs/api-guide/serializers#modelserializer)
+An alternative method uses more of Django Rest Framework's features, the [ModelSerializer](https://www.django-rest-framework.org/api-guide/serializers/#modelserializer)
 
 ```python
 from rest_framework import serializers
diff --git a/develop-docs/backend/application-domains/options.mdx b/develop-docs/backend/application-domains/options.mdx
@@ -13,7 +13,7 @@ While the process for creating and using options in the codebase is universal, t
 
 ## Adding New Options
 
-The process for registering a new option is the same for all environments and is done in the Sentry codebase. Add your option to [`sentry/options/defaults.py`](https://github.com/getsentry/sentry/blob/master/sentry/options/defaults.py).
+The process for registering a new option is the same for all environments and is done in the Sentry codebase. Add your option to [`sentry/options/defaults.py`](https://github.com/getsentry/sentry/blob/master/src/sentry/options/defaults.py).
 
 ```python
 register("performance.some-feature-rate", default=0.0)
diff --git a/develop-docs/backend/application-domains/translations.mdx b/develop-docs/backend/application-domains/translations.mdx
@@ -3,7 +3,7 @@ title: Translations
 sidebar_order: 40
 ---
 
-We use [**Transifex**](https://www.transifex.com/getsentry/sentry) to translate Sentry.
+We use [**Transifex**](https://explore.transifex.com/getsentry/sentry/) to translate Sentry.
 
 Other things that mean translating: localization, internationalization, i18n, l10n
 
diff --git a/develop-docs/frontend/index.mdx b/develop-docs/frontend/index.mdx
@@ -118,7 +118,7 @@ Prefer the built-in `useState` and `useReducer` react hooks for state whenever p
 
 We currently also have [Reflux](https://github.com/reflux/refluxjs) and [MobX](https://github.com/mobxjs/mobx) included in package.json but their use for new cases is discouraged.
 
-Reflux implements the unidirectional data flow pattern outlined by [Flux](https://facebook.github.io/flux/). Stores are registered under `app/stores` and are used to store various pieces of data used by the application. Actions need to be registered under `app/actions`. We use action creator functions (under `app/actionCreators`) to dispatch actions. Reflux stores listen to actions and update themselves accordingly.
+Reflux implements the unidirectional data flow pattern outlined by [Flux](https://facebookarchive.github.io/flux). Stores are registered under `app/stores` and are used to store various pieces of data used by the application. Actions need to be registered under `app/actions`. We use action creator functions (under `app/actionCreators`) to dispatch actions. Reflux stores listen to actions and update themselves accordingly.
 
 ## Testing
 
diff --git a/develop-docs/sdk/data-model/event-payloads/index.mdx b/develop-docs/sdk/data-model/event-payloads/index.mdx
@@ -24,7 +24,8 @@ code.
 
 <Alert title="Found a problem?" level="warning"><markdown>
 
-If documentation is lacking or outdated, please let us know by [opening an issue](https://github.com/getsentry/develop/issues/new).
+If documentation is lacking or outdated, please let us know by [opening an issue](https://github.com/getsentry/sentry-docs/issues/new?template=issue-content-03-develop.yml).
+
 
 SDK developers might benefit from consulting the [documentation](https://getsentry.github.io/relay/relay_event_schema/protocol/index.html) and [source code](https://github.com/getsentry/relay/tree/master/relay-event-schema/src/protocol) defining the protocol as understood by the server.
 
diff --git a/develop-docs/sdk/telemetry/traces/span-data-conventions.mdx b/develop-docs/sdk/telemetry/traces/span-data-conventions.mdx
@@ -66,8 +66,8 @@ Below describes the conventions for the Span interface for the `data` field on t
 
 | Attribute               | Type   | Description                                                                                                                                                                                                                                                                                                                | Examples      |
 | ----------------------- | ------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------- |
-| `db.system`             | string | An identifier for the database management system (DBMS) product being used. See [OpenTelemetry docs for a list of well-known identifiers](https://github.com/open-telemetry/semantic-conventions/blob/main/docs/database/database-spans.md#notes-and-well-known-identifiers-for-dbsystem).     | `postgresql`  |
-| `db.operation`          | string | The name of the operation being executed, e.g. the MongoDB command name such as findAndModify, or the SQL keyword. Based on [OpenTelemetry's common db attributes](https://github.com/open-telemetry/semantic-conventions/blob/main/docs/database/database-spans.md#common-attributes) | `SELECT`      |
+| `db.system`             | string | An identifier for the database management system (DBMS) product being used. See [OpenTelemetry docs for a list of well-known identifiers](https://opentelemetry.io/docs/specs/semconv/database/).     | `postgresql`  |
+| `db.operation`          | string | The name of the operation being executed, e.g. the MongoDB command name such as findAndModify, or the SQL keyword. Based on [OpenTelemetry's database semantic conventions](https://opentelemetry.io/docs/specs/semconv/database/) | `SELECT`      |
 | `db.collection.name`    | string | The name of the collection (or table, etc) being queried.                                                                                                                                                                                                                                                                  | `users`       |
 | `db.name`               | string | This attribute is used to report the name of the database being accessed. For commands that switch the database, this should be set to the target database (even if the command fails).                                                                                                                                    | `customers`   |
 | `server.address`        | string | Name of the database host.                                                                                                                                                                                                                                                                                                 | `example.com` |
diff --git a/develop-docs/sdk/telemetry/traces/span-operations.mdx b/develop-docs/sdk/telemetry/traces/span-operations.mdx
@@ -141,7 +141,7 @@ Web server related spans should aim to follow OpenTelemetry's [HTTP](https://git
 
 ## Database
 
-Databased related spans are expected to follow OpenTelemetry's [Database](https://github.com/open-telemetry/semantic-conventions/blob/main/docs/database/database-spans.md) semantic conventions when possible.
+Databased related spans are expected to follow OpenTelemetry's [Database](https://opentelemetry.io/docs/specs/semconv/database/) semantic conventions when possible.
 
 | Category | Usage                | Description                |
 | -------- | -------------------- | -------------------------- |
diff --git a/develop-docs/self-hosted/configuration/email.mdx b/develop-docs/self-hosted/configuration/email.mdx
@@ -25,4 +25,4 @@ Sentry does not support sending outbound email with any other protocol than SMTP
 
 ## Inbound Email
 
-Sentry has very limited inbound mail support through [Mailgun](https://documentation.mailgun.com/en/latest/quickstart-receiving.html). You can find all the information regarding how to set this up over at our [inbound email service documentation](/backend/email/#inbound-email).
+Sentry has very limited inbound mail support through [Mailgun](https://documentation.mailgun.com/docs/mailgun/user-manual/receive-forward-store/receive-forward-store). You can find all the information regarding how to set this up over at our [inbound email service documentation](/backend/email/#inbound-email).
diff --git a/docs/concepts/data-management/event-grouping/index.mdx b/docs/concepts/data-management/event-grouping/index.mdx
@@ -62,7 +62,7 @@ In addition to fingerprint-based grouping, Sentry uses AI to further improve iss
 
 This system will not apply to any events that have fully custom fingerprints (either set via SDK or [fingerprint rules](/product/issues/grouping-and-fingerprints/#fingerprint-rules)). However, events with fingerprints containing `{{ default }}` will use AI grouping to calculate the `{{ default }}` portion of the fingerprint.
 
-When Sentry's default fingerprinting algorithm generates a new hash, it automatically sends the error data to [Seer](https://github.com/getsentry/seer), our AI/ML service. That error data includes the message and in-app stack frames (including those configured with stack trace rules), or all frames when no in-app frames are present.
+When Sentry's default fingerprinting algorithm generates a new hash, it automatically sends the error data to Seer, our AI/ML service. That error data includes the message and in-app stack frames (including those configured with stack trace rules), or all frames when no in-app frames are present.
 
 Seer performs the following steps:
 
diff --git a/docs/organization/authentication/sso/ping-sso.mdx b/docs/organization/authentication/sso/ping-sso.mdx
@@ -19,7 +19,7 @@ If you change your organization slug, you'll need to make the same update in the
 
 1. If you don't require a permission group for Sentry, skip to step 5.
 
-1. In the sidebar, click on "Identities", then "Groups", and navigate to it. From there, create a new group and add yourself and other members to it. For more details about group creation, see the [Ping ID docs](https://docs.pingidentity.com/bundle/pingone/page/vdz1610472224361.html).
+1. In the sidebar, click on "Identities", then "Groups", and navigate to it. From there, create a new group and add yourself and other members to it. For more details about group creation, see the [Ping Identity documentation](https://docs.pingidentity.com/pingone).
 
 1. In the sidebar, click on "Connections", then "Applications". Click on "+ Application" and for the application type, select "Web App" and "SAML".
 
diff --git a/docs/organization/integrations/feature-flag/flagsmith/index.mdx b/docs/organization/integrations/feature-flag/flagsmith/index.mdx
@@ -16,7 +16,7 @@ Flagsmith recommends using an OpenFeature SDK combined with a [Flagsmith provide
 * [Python](/platforms/python/integrations/openfeature/)
 * [Java (through OpenFeature)](/platforms/java/integrations/openfeature/)
 
-Visit the [Flagsmith documentation](https://docs.flagsmith.com/integrations/apm/sentry#evaluation-tracking-setup) for specific instructions on how to set up the OpenFeature SDK with the Flagsmith provider.
+Visit the [Flagsmith documentation](https://docs.flagsmith.com/third-party-integrations/observability-and-monitoring/sentry) for specific instructions on how to set up the OpenFeature SDK with the Flagsmith provider.
 
 ## Change Tracking
 
diff --git a/docs/platforms/apple/common/troubleshooting/index.mdx b/docs/platforms/apple/common/troubleshooting/index.mdx
@@ -68,7 +68,7 @@ Suppose your app crashes in `SentrySubClassFinder actOnSubclassesOfViewControlle
 #10	0x000000010514b4c0 in __69-[SentrySubClassFinder actOnSubclassesOfViewControllerInImage:block:]
 ```
 
-Such a crash may be due to a [potential bug in Swift](https://github.com/apple/swift/issues/72657)
+Such a crash may be due to a [potential bug in Swift](https://github.com/swiftlang/swift/issues/72657)
 that's triggered when trying to get a class definition that references a RoomPlan or
 ActivityKit class on an older iOS version that doesn't support RoomPlan or ActivityKit.
 For example, running the code below on iOS 15 with the Sentry Cocoa SDK enabled
diff --git a/docs/platforms/dotnet/guides/xamarin/troubleshooting.mdx b/docs/platforms/dotnet/guides/xamarin/troubleshooting.mdx
@@ -83,7 +83,7 @@ One solution is to alter your DSN; to do this, remove the values between `@` and
 - Before: `https://abc@1234.ingest.sentry.io/1234`
 - After: `https://abc@sentry.io/1234`
 
-Find more information here: https://github.com/xamarin/xamarin-android/issues/6351
+Find more information here: https://github.com/dotnet/android/issues/6351
 
 ## tvOS
 
diff --git a/platform-includes/distributed-tracing/how-to-use/javascript.remix.mdx b/platform-includes/distributed-tracing/how-to-use/javascript.remix.mdx
@@ -1,4 +1,4 @@
-Remix SDK attaches `sentry-trace` and `baggage` values from your `root` loader. You need to use the [`meta`](https://remix.run/docs/en/v1/api/conventions#meta) function to attach the data from your `loader` as `<meta>` tags. The following code snippet shows how to do this:
+Remix SDK attaches `sentry-trace` and `baggage` values from your `root` loader. You need to use the [`meta`](https://remix.run/docs/en/main/route/meta) function to attach the data from your `loader` as `<meta>` tags. The following code snippet shows how to do this:
 
 ```typescript {tabTitle: Remix v1} {filename: root.tsx}
 export const meta: MetaFunction = ({ data }) => {
diff --git a/platform-includes/migration/javascript-v8/troubleshooting/javascript.nextjs.mdx b/platform-includes/migration/javascript-v8/troubleshooting/javascript.nextjs.mdx
@@ -6,7 +6,7 @@
 
 If you are using a [Next.js custom server](https://nextjs.org/docs/pages/building-your-application/configuring/custom-server), the `instrumentation.ts|js` hook is not called by Next.js so you need to manually call it yourself from within your server code. It is recommended to do so as early as possible in your application lifecycle.
 
-Here's an example of adding Sentry initialization code to the custom server example as per the [Next.js documentation](https://nextjs.org/docs/advanced-features/custom-server):
+Here's an example of adding Sentry initialization code to the custom server example as per the [Next.js documentation](https://nextjs.org/docs/pages/building-your-application/configuring/custom-server):
 
 ```JavaScript diff {server.js} {1}
 // make sure that Sentry is imported and initialized before any other imports.
diff --git a/platform-includes/performance/connect-services/javascript.mdx b/platform-includes/performance/connect-services/javascript.mdx
@@ -34,7 +34,7 @@ For traces that begin in your backend, you can connect the automatically-generat
 
 <PlatformSection supported={["javascript.remix"]} notSupported={["javascript"]}>
 
-Remix SDK attaches `sentry-trace` and `baggage` values from your `root` loader. You need to use [`meta`](https://remix.run/docs/en/v1/api/conventions#meta) function to attach the data from your `loader` as `<meta>` tags. The following code snippet shows how to do this:
+Remix SDK attaches `sentry-trace` and `baggage` values from your `root` loader. You need to use the [`meta`](https://remix.run/docs/en/main/route/meta) function to attach the data from your `loader` as `<meta>` tags. The following code snippet shows how to do this:
 
 ```typescript {filename: root.tsx}
 export const meta: MetaFunction = ({ data }) => {

Original file line number	Diff line number	Diff line change
`@@ -25,4 +25,4 @@ Sentry does not support sending outbound email with any other protocol than SMTP`
`25`	`25`
`26`	`26`	`## Inbound Email`
`27`	`27`
`28`		`-Sentry has very limited inbound mail support through [Mailgun](https://documentation.mailgun.com/en/latest/quickstart-receiving.html). You can find all the information regarding how to set this up over at our [inbound email service documentation](/backend/email/#inbound-email).`
	`28`	`+Sentry has very limited inbound mail support through [Mailgun](https://documentation.mailgun.com/docs/mailgun/user-manual/receive-forward-store/receive-forward-store). You can find all the information regarding how to set this up over at our [inbound email service documentation](/backend/email/#inbound-email).`