Fix broken links

Author: markstory

develop-docs/backend/issue-platform-detectors/index.mdx

@@ -3,7 +3,7 @@ title: Issue Platform - Writing Detectors
 sidebar_order: 90
 ---
 
-Issue detectors identify application issues by examining one or more datasets collected by Sentry, and report detected issue occurrences via the <Link to="/issue-platform/">Issue Platform</Link>. Detectors must fingerprint issues accurately and provide actionable information to developers.
+Issue detectors identify application issues by examining one or more datasets collected by Sentry, and report detected issue occurrences via the <Link to="/backend/issue-platform/">Issue Platform</Link>. Detectors must fingerprint issues accurately and provide actionable information to developers.
 
 # Considerations
 

develop-docs/backend/issue-platform/index.mdx

@@ -16,7 +16,7 @@ To use the Issue Platform you need to:
 
 The first step to introducing a new issue type to Sentry is to determine what type of issue you want to detect. It can be from any data stream, as long as you can produce an <Link to="#issue-occurrence-schema">Occurrence</Link> representing the issue.
 
-Writing a detector is the hardest part of creating a new issue type. Refer to <Link to="/issue-platform-detectors/">this guide</Link> for tips on how to write one.
+Writing a detector is the hardest part of creating a new issue type. Refer to <Link to="/backend/issue-platform-detectors/">this guide</Link> for tips on how to write one.
 
 ## Register an Issue Type
 

develop-docs/backend/pii/index.mdx

@@ -50,10 +50,10 @@ The following rules exist by default:
 
 Rules generally consist of two parts:
 
-- _Rule types_ describe what to match. See <Link to="/pii/types/">PII Rule
+- _Rule types_ describe what to match. See <Link to="/backend/pii/types/">PII Rule
   Types</Link> for an exhaustive list.
 - _Rule redaction methods_ describe what to do with the match. See <Link
-  to="/pii/methods/">PII Redaction Methods</Link> for a list.
+  to="/backend/pii/methods/">PII Redaction Methods</Link> for a list.
 
 Each page comes with examples. Try those examples out by pasting them into the
 "PII config" column of [Piinguin] and clicking on fields to get suggestions.

develop-docs/development/environment/index.mdx

@@ -116,7 +116,7 @@ sentry devservices up snuba
   Only Sentry employees have access to getsentry.
 </Alert>
 
-See also: <Link to="/sentry-vs-getsentry/">Sentry vs Getsentry</Link>
+See also: <Link to="/application/sentry-vs-getsentry/">Sentry vs Getsentry</Link>
 
 Before running `getsentry`, you might need to run `devenv sync` inside the `getsentry` directory if you have previously run `sentry` locally, as there might be differences between the environments.
 
@@ -149,7 +149,7 @@ getsentry devserver --workers --ingest
 
 ## Running siloed instances
 
-By default `sentry devserver` will run a monolith mode application server. You can also run `devserver` with siloed application instances. Before you do, you need to <Link to="/database-migrations/#cloning-a-monolith-database">create split silo databases</Link>.
+By default `sentry devserver` will run a monolith mode application server. You can also run `devserver` with siloed application instances. Before you do, you need to <Link to="/backend/database-migrations/#cloning-a-monolith-database">create split silo databases</Link>.
 
 The devserver command supports `--silo` option that lets you create siloed instances. Any workers, consumers, or celery-beat processes will be started with the same silo mode.
 
@@ -187,7 +187,7 @@ SENTRY_SILO_DEVSERVER=1 SENTRY_SILO_MODE=REGION SENTRY_REGION=us getsentry djang
 
 ## Troubleshooting
 
-You might also be interested in <Link to="/continuous-integration/#troubleshooting-ci">troubleshooting CI</Link>.
+You might also be interested in <Link to="/development/continuous-integration/#troubleshooting-ci">troubleshooting CI</Link>.
 
 ---
 

develop-docs/development/environment/ports.mdx

@@ -10,16 +10,16 @@ The following is a non-exhaustive list of ports used by Sentry services or any d
 
 | Port | Service                                    | Description
 |:-----|:-------------------------------------------|:-----------
-| 9000 | Clickhouse                                 | <Link to="/services/devservices/">Devservice</Link> `clickhouse`. Database for Snuba.
+| 9000 | Clickhouse                                 | <Link to="/development/devservices/">Devservice</Link> `clickhouse`. Database for Snuba.
 | 8123 | Clickhouse                                 |
 | 9009 | Clickhouse                                 |
-| 3021 | Symbolicator                               | <Link to="/services/devservices/">Devservice</Link> `symbolicator`. For processing stacktraces.
-| 1218 | [Snuba][]                                  | <Link to="/services/devservices/">Devservice</Link> `snuba`. For searching events.
+| 3021 | Symbolicator                               | <Link to="/development/devservices/">Devservice</Link> `symbolicator`. For processing stacktraces.
+| 1218 | [Snuba][]                                  | <Link to="/development/devservices/">Devservice</Link> `snuba`. For searching events.
 | 1219 | [Snuba][] admin                            | Not part of devservices setup, but running `snuba admin` will listen on this port.
-| 9092 | Kafka                                      | <Link to="/services/devservices/">Devservice</Link> `kafka`. for relay-sentry communication and optionally for sentry-snuba communication
-| 6379 | Redis                                      | <Link to="/services/devservices/">Devservice</Link> `redis` (or perhaps installed via Homebrew in rustier setups), responsible for caches, relay projectconfigs and Celery queues
-| 5432 | Postgres                                   | <Link to="/services/devservices/">Devservice</Link> `postgres` (or perhaps installed via Homebrew in rustier setups)
-| 7899 | [Relay][]                                  | <Link to="/services/devservices/">Devservice</Link> `relay`. Serves APIs for SDKs to send events to (aka event ingestion). Webpack on 8000 reverse-proxies to this server. Starts/stops with `sentry devserver`.
+| 9092 | Kafka                                      | <Link to="/development/devservices/">Devservice</Link> `kafka`. for relay-sentry communication and optionally for sentry-snuba communication
+| 6379 | Redis                                      | <Link to="/development/devservices/">Devservice</Link> `redis` (or perhaps installed via Homebrew in rustier setups), responsible for caches, relay projectconfigs and Celery queues
+| 5432 | Postgres                                   | <Link to="/development/devservices/">Devservice</Link> `postgres` (or perhaps installed via Homebrew in rustier setups)
+| 7899 | [Relay][]                                  | <Link to="/development/devservices/">Devservice</Link> `relay`. Serves APIs for SDKs to send events to (aka event ingestion). Webpack on 8000 reverse-proxies to this server. Starts/stops with `sentry devserver`.
 | 8000 | <Link to="/development/environment/">Sentry Dev</Link> | Webpack devserver, routing all ingest paths to Relay, and the rest to uWSGI. Routing is defined in `webpack.config.ts` in Sentry.
 | 8001 | uWSGI                                      | Starts/stops with `sentry devserver`. Serves the Django app/API. Webpack on 8000 reverse-proxies to this server. In a siloed devserver, this port is used for control silo.
 | 8010 | uWSGI (region silo)                        | Starts/stops with `sentry devserver --silo=region`. Serves the Django app/API. Webpack on 8000 reverse-proxies to this server.

develop-docs/development/ngrok.mdx

@@ -61,11 +61,11 @@ getsentry devserver --ngrok=<yourname>.ngrok.io
 
 To debug issues related to integration middleware as well as issues relating to latency induced by RPC calls, you can run your local environment in silo mode.
 
-To learn more about how silo mode works in the dev environment, refer to <Link to="/environment/#running-siloed-instances"> Running Siloed Instances</Link>.
+To learn more about how silo mode works in the dev environment, refer to <Link to="/development/environment/#running-siloed-instances"> Running Siloed Instances</Link>.
 
 
 ### Step 1: Split Local DB into Silos
-By default `sentry devserver` will run a monolith mode application server. You can also run ``devserver`` with siloed application instances. Before you do, you need to <Link to="/database-migrations/#cloning-a-monolith-database">create split silo databases</Link>.
+By default `sentry devserver` will run a monolith mode application server. You can also run ``devserver`` with siloed application instances. Before you do, you need to <Link to="/backend/database-migrations/#cloning-a-monolith-database">create split silo databases</Link>.
 
 
 ### Step 2: Create Ngrok Config File

develop-docs/development/workflow.mdx

@@ -3,7 +3,7 @@ title: Workflow
 sidebar_order: 40
 ---
 
-You may also be interested in <Link to="/sentry-vs-getsentry/">sentry vs. getsentry</Link>.
+You may also be interested in <Link to="/application/sentry-vs-getsentry/">sentry vs. getsentry</Link>.
 
 
 ## Testing Sentry commits in Getsentry