feat(uptime): migrate uptime pages upwards and add redirects

docs/product/alerts/alert-types.mdx

@@ -116,7 +116,7 @@ The **Alert Details** page also includes a list of suspect issues or transaction
 
 ## Uptime Alerts
 
-Uptime alerts trigger whenever an uptime check request fails to meet our [uptime check criteria](/product/alerts/uptime-monitoring/#uptime-check-criteria). You'll be able to see the latest uptime check request status ("Up" or "Down") in the “Alert Rules” tab.
+Uptime alerts trigger whenever an uptime check request fails to meet our [uptime check criteria](/product/uptime-monitoring/#uptime-check-criteria). You'll be able to see the latest uptime check request status ("Up" or "Down") in the “Alert Rules” tab.
 
 ### Alert Details
 

docs/product/alerts/create-alerts/uptime-alert-config.mdx

@@ -28,7 +28,7 @@ Configure how Sentry performs HTTP uptime checks by setting the following option
 - **Method**: The HTTP method used (`GET`, `POST`, `HEAD`, `PUT`, `DELETE`, `PATCH`, or `OPTIONS`).
 - **Headers**: Custom headers included in the request.
 - **Body**: The request payload, available for `POST`, `PUT`, and `PATCH` methods.
-- **Allow Sampling**: Enables span sampling for requests via the Sentry SDK. See [distributed tracing with uptime](/product/alerts/uptime-monitoring/uptime-tracing/) for details.
+- **Allow Sampling**: Enables span sampling for requests via the Sentry SDK. See [distributed tracing with uptime](/product/uptime-monitoring/uptime-tracing/) for details.
 
 <Alert level="warning">
 
@@ -43,9 +43,9 @@ Below the request configuration, you'll find an example of the expected request
 Additional notes:
 
 - Include a `Content-Type` header if required by the target URL. For example, a JSON payload should have `Content-Type: application/json`.
-- The selected interval affects downtime detection speed. Sentry triggers an uptime issue after three consecutive failures. For instance, with a 5-minute interval, downtime is detected at least 15 minutes after the first failure. Learn more about the [uptime check criteria](/product/alerts/uptime-monitoring/#uptime-check-criteria).
-- In case the specified URL is behind a firewall, make sure Sentry's Uptime Bot can execute requests to it. Learn more about [firewall configuration with uptime monitoring](/product/alerts/uptime-monitoring/troubleshooting/#verify-firewall-configuration).
-- Sentry Uptime Tracing automatically appends a sentry-trace header to outgoing requests for distributed tracing. [Learn more](/product/alerts/uptime-monitoring/uptime-tracing/).
+- The selected interval affects downtime detection speed. Sentry triggers an uptime issue after three consecutive failures. For instance, with a 5-minute interval, downtime is detected at least 15 minutes after the first failure. Learn more about the [uptime check criteria](/product/uptime-monitoring/#uptime-check-criteria).
+- In case the specified URL is behind a firewall, make sure Sentry's Uptime Bot can execute requests to it. Learn more about [firewall configuration with uptime monitoring](/product/uptime-monitoring/troubleshooting/#verify-firewall-configuration).
+- Sentry Uptime Tracing automatically appends a sentry-trace header to outgoing requests for distributed tracing. [Learn more](/product/uptime-monitoring/uptime-tracing/).
 
 ## 4. Alert Name
 

docs/product/alerts/index.mdx

@@ -38,8 +38,8 @@ You can find a full list of available metric alerts in [Metric Alerts](/product/
 
 ## Uptime Monitoring Alerts
 
-[Uptime alerts](/product/alerts/uptime-monitoring/) are triggered when an uptime HTTP check request fails to meet our
-[uptime check criteria](/product/alerts/uptime-monitoring/#uptime-check-criteria).
+[Uptime alerts](/product/uptime-monitoring/) are triggered when an uptime HTTP check request fails to meet our
+[uptime check criteria](/product/uptime-monitoring/#uptime-check-criteria).
 You can use uptime alerts to make sure a specific URL is constantly available, even during periods of low or no traffic.
 
 ## Creating Alerts

docs/product/index.mdx

@@ -50,7 +50,7 @@ Our [**LLM Monitoring**](/product/insights/llm-monitoring/) feature gives you in
 
 ### Uptime Monitoring
 
-Sentry's [**Uptime Monitoring**](/product/alerts/uptime-monitoring/) helps you maintain uptime for your web services by monitoring relevant URLs. It continuously tracks configured URLs, delivering alerts and insights to quickly identify downtime and troubleshoot issues. By leveraging [distributed tracing](/product/alerts/uptime-monitoring/uptime-tracing/), Sentry enables you to pinpoint any errors that occur during an uptime check, simplifying triage and accelerating root cause analysis.
+Sentry's [**Uptime Monitoring**](/product/uptime-monitoring/) helps you maintain uptime for your web services by monitoring relevant URLs. It continuously tracks configured URLs, delivering alerts and insights to quickly identify downtime and troubleshoot issues. By leveraging [distributed tracing](/product/uptime-monitoring/uptime-tracing/), Sentry enables you to pinpoint any errors that occur during an uptime check, simplifying triage and accelerating root cause analysis.
 
 ### Recurring Job Monitoring
 

docs/product/issues/issue-details/uptime-issues/index.mdx

@@ -6,15 +6,15 @@ description: "Learn how to use the information on the Issue Details page to debu
 
 An uptime issue is a grouping of detected downtime events for a specific URL. A downtime event is generated by
 active uptime alerts when HTTP requests fail to meet our
-[uptime check criteria](/product/alerts/uptime-monitoring/#uptime-check-criteria).
+[uptime check criteria](/product/uptime-monitoring/#uptime-check-criteria).
 
 ![Uptime issue details](./img/uptime-issue-details.png)
 
 ## Traced Errors
 
 Uptime checks made against web services configured with one of Sentry's supported SDKs contain a
-[trace](/concepts/key-terms/tracing/) that can be used to track detected errors resulting from failed HTTP uptime checks. The trace navigator allows you to browse through potential root causes of your downtime and is a powerful  tool for quickly identifying and resolving issues.
+[trace](/concepts/key-terms/tracing/) that can be used to track detected errors resulting from failed HTTP uptime checks. The trace navigator allows you to browse through potential root causes of your downtime and is a powerful tool for quickly identifying and resolving issues.
 
 ## Issue Lifecycle
 
-Uptime issues are grouped by the monitored URL and created upon the first detected downtime. Sentry automatically resolves an ongoing uptime issue when the monitored URL returns to a healthy status and meets our [uptime check criteria](/product/alerts/uptime-monitoring/#uptime-check-criteria). If the URL experiences subsequent downtime, the issue's status will change to regressed.
+Uptime issues are grouped by the monitored URL and created upon the first detected downtime. Sentry automatically resolves an ongoing uptime issue when the monitored URL returns to a healthy status and meets our [uptime check criteria](/product/uptime-monitoring/#uptime-check-criteria). If the URL experiences subsequent downtime, the issue's status will change to regressed.

docs/product/alerts/uptime-monitoring/automatic-detection.mdx → docs/product/uptime-monitoring/automatic-detection.mdx

@@ -4,14 +4,17 @@ sidebar_order: 51
 description: "Learn how automatic detection of uptime monitoring works."
 ---
 
-In order to be able to automatically detect uptime alerts, we analyze all the URLs detected in your project's captured error data to find the hostname that appears most frequently. This helps ensure that your most critical hostname is continuously monitored, enhancing the reliability and availability of your web services. We then create an uptime alert if it passes our [uptime check criteria](/product/alerts/uptime-monitoring/#uptime-check-criteria). Automatic uptime checks are configured to run once a minute as GET requests.
+In order to be able to automatically detect uptime alerts, we analyze all the URLs detected in your project's captured error data to find the hostname that appears most frequently. This helps ensure that your most critical hostname is continuously monitored, enhancing the reliability and availability of your web services. We then create an uptime alert if it passes our [uptime check criteria](/product/uptime-monitoring/#uptime-check-criteria). Automatic uptime checks are configured to run once a minute as GET requests.
 
-The automatic creation of Uptime Monitors only happens if there are no other existing uptime monitors configured. 
+The automatic creation of Uptime Monitors only happens if there are no other existing uptime monitors configured.
 
 To avoid creating flaky alerts, the hostname undergoes an "onboarding period" of three days. During this period, we send HTTP requests to the hostname every hour. If the request fails three times or more, the hostname will be dropped and re-evaluated after seven days.
 
 <Alert>
- Sentry will execute uptime checks against the hostname root path of the most frequently-seen URLs. For example, if the most frequently-seen URL in your events is `GET https://www.example.com/docs/introduction`, the check will be `GET https://www.example.com/`.
+  Sentry will execute uptime checks against the hostname root path of the most
+  frequently-seen URLs. For example, if the most frequently-seen URL in your
+  events is `GET https://www.example.com/docs/introduction`, the check will be
+  `GET https://www.example.com/`.
 </Alert>
 
 Once an automatically detected uptime alert has been created, you'll be able to [customize its configuration](/product/alerts/create-alerts/uptime-alert-config/), including the HTTP request method, headers, and request body.
@@ -29,5 +32,7 @@ Disallow: *
 ```
 
 <Alert level="warning">
-**Note:** The `robots.txt` file only prevents Sentry from detecting URLs that it encounters after its been implemented. Existing URLs that have already been detected will continue to have uptime alerts unless they're manually deleted.
+  **Note:** The `robots.txt` file only prevents Sentry from detecting URLs that
+  it encounters after its been implemented. Existing URLs that have already been
+  detected will continue to have uptime alerts unless they're manually deleted.
 </Alert>

docs/product/alerts/uptime-monitoring/index.mdx → docs/product/uptime-monitoring/index.mdx

@@ -10,7 +10,7 @@ By leveraging [distributed tracing](/concepts/key-terms/tracing/distributed-trac
 
 ## Set Up
 
-Uptime is [automatically configured](/product/alerts/uptime-monitoring/automatic-detection/) as a new alert for the most frequently encountered hostname in all URLs of your error data, ensuring continuous monitoring of your most critical hostname right out of the box.
+Uptime is [automatically configured](/product/uptime-monitoring/automatic-detection/) as a new alert for the most frequently encountered hostname in all URLs of your error data, ensuring continuous monitoring of your most critical hostname right out of the box.
 
 You can also [create uptime monitoring alerts](/product/alerts/create-alerts/) for specific URLs. They're fully customizable with request details such as the HTTP method, headers, and body.
 

docs/product/alerts/uptime-monitoring/troubleshooting.mdx → docs/product/uptime-monitoring/troubleshooting.mdx

@@ -15,7 +15,7 @@ If you need to configure your firewall allowlist to include Sentry's Uptime Bot,
 Our uptime check requests use the following `User-Agent`:
 
 ```
-SentryUptimeBot/1.0 (+http://docs.sentry.io/product/alerts/uptime-monitoring/)
+SentryUptimeBot/1.0 (+http://docs.sentry.io/product/uptime-monitoring/)
 ```
 
 ### IP Addresses

docs/product/alerts/uptime-monitoring/uptime-tracing.mdx → docs/product/uptime-monitoring/uptime-tracing.mdx

@@ -19,7 +19,7 @@ Example Uptime check request:
 ```HTTP
 GET /example-uptime-endpoint HTTP/1.1
 Host: sentry.io
-User-Agent: SentryUptimeBot/1.0 (+http://docs.sentry.io/product/alerts/uptime-monitoring/)
+User-Agent: SentryUptimeBot/1.0 (+http://docs.sentry.io/product/uptime-monitoring/)
 Sentry-Trace: 32d4011600324838afcd666edadc1d09-8d5ca7419a02ca36
 ```
 

docs/security-legal-pii/security/ip-ranges.mdx

@@ -158,6 +158,6 @@ This endpoint returns a newline-separated list of all current Uptime Monitoring
 
 <Alert title="Note" level="warning">
 
-Uptime Monitoring IP addresses may change over time. If you need to programmatically verify whether a visitor is a Sentry bot, we recommend checking the [user agent](/product/alerts/uptime-monitoring/troubleshooting/#user-agent) instead.
+Uptime Monitoring IP addresses may change over time. If you need to programmatically verify whether a visitor is a Sentry bot, we recommend checking the [user agent](/product/uptime-monitoring/troubleshooting/#user-agent) instead.
 
 </Alert>

src/middleware.ts

@@ -4033,6 +4033,23 @@ const DEVELOPER_DOCS_REDIRECTS: Redirect[] = [
     from: '/organization/integrations/elba/',
     to: '/organization/integrations/compliance/elba/',
   },
+  /* Uptime Monitoring */
+  {
+    from: '/product/alerts/uptime-monitoring/',
+    to: '/product/uptime-monitoring/',
+  },
+  {
+    from: '/product/alerts/uptime-monitoring/automatic-detection/',
+    to: '/product/uptime-monitoring/automatic-detection/',
+  },
+  {
+    from: '/product/alerts/uptime-monitoring/uptime-tracing/',
+    to: '/product/uptime-monitoring/uptime-tracing/',
+  },
+  {
+    from: '/product/alerts/uptime-monitoring/troubleshooting/',
+    to: '/product/uptime-monitoring/troubleshooting/',
+  },
 ];
 
 const redirectMap = new Map(