getsentry · sfanahata · Apr 14, 2026 · Apr 14, 2026 · Apr 15, 2026 · Apr 15, 2026
diff --git a/develop-docs/self-hosted/optional-features/errors-only.mdx b/develop-docs/self-hosted/optional-features/errors-only.mdx
@@ -27,7 +27,7 @@ This is our default version of self-hosted Sentry. It includes most of the featu
 4. [Insights](https://docs.sentry.io/product/insights/) (Requests, Queries, Assets, etc)
 5. [User Feedback](https://docs.sentry.io/product/user-feedback/)
 6. [Insights](https://docs.sentry.io/product/insights/)
-7. [Crons](https://docs.sentry.io/product/crons/)
+7. [Crons](https://docs.sentry.io/product/monitors-and-alerts/monitors/crons/)
 8. [Metrics](https://docs.sentry.io/product/explore/metrics/)
 
 This version of Sentry is enabled by default upon installation. Ensure that your [.env file](https://github.com/getsentry/self-hosted/blob/master/.env) includes `COMPOSE_PROFILES=feature-complete`.
diff --git a/docs/account/user-settings/index.mdx b/docs/account/user-settings/index.mdx
@@ -35,7 +35,7 @@ In **Notifications**, you can configure your personal settings for the following
 
 You can also set your email routing here.
 
-Learn more in the [full Notifications documentation](/product/alerts/notifications/).
+Learn more in the [full Notifications documentation](/product/notifications/).
 
 ## Emails
 

diff --git a/docs/cli/configuration.mdx b/docs/cli/configuration.mdx
@@ -27,7 +27,7 @@ You can manually create an [Organization Token](https://sentry.io/orgredirect/or
 You can also sign in to your Sentry account (if you're not already) and create an Auth Token directly from this page.
 
 <Alert>
-Some CLI functionality, such as [Crons Monitoring](/product/crons/getting-started/cli/), is dependent on [Data Source Name (DSN)](/concepts/key-terms/dsn-explainer/) authentication.
+Some CLI functionality, such as [Crons Monitoring](/cli/crons/), is dependent on [Data Source Name (DSN)](/concepts/key-terms/dsn-explainer/) authentication.
 </Alert>
 
 You can create an Auth Token from this page in one of the following three ways:

diff --git a/docs/cli/crons.mdx b/docs/cli/crons.mdx
@@ -84,7 +84,7 @@ sentry-cli monitors run -s "0 * * * *" --check-in-margin 10 --max-runtime 5 --ti
 
 ### Specifying Monitor Environments (Optional)
 
-If your cron monitor runs in multiple environments you can use the `-e` flag to specify which [Monitor Environment](/product/crons/job-monitoring/#multiple-environments) to send check-ins to.
+If your cron monitor runs in multiple environments you can use the `-e` flag to specify which [Monitor Environment](/product/monitors-and-alerts/monitors/crons/job-monitoring/#multiple-environments) to send check-ins to.
 
 ```bash {tabTitle: Node.JS}
 sentry-cli monitors run -e dev my-monitor-slug -- node path/to/file.js

diff --git a/docs/guides/logs.mdx b/docs/guides/logs.mdx
@@ -788,7 +788,7 @@ Sentry.logger().warn("Config reloaded reason=%s", "env-change")
    - **Anomaly:** Let Sentry detect unusual patterns
 5. Configure notification channels and save
 
-Learn about [creating alerts](/product/new-monitors-and-alerts/alerts/) and best practices for [reducing noise and routing notifications](/product/new-monitors-and-alerts/alerts/best-practices/).
+Learn about [creating alerts](/product/monitors-and-alerts/alerts/) and [notifications](/product/notifications/).
 
 ## Logging Strategy
 

diff --git a/docs/guides/querying-traces.mdx b/docs/guides/querying-traces.mdx
@@ -74,7 +74,7 @@ Start with these five queries and you'll catch most performance issues before us
 
 **Tip:** Averages can hide outliers, use p75/p90/p95 instead.
 
-Learn about [creating alerts](/product/new-monitors-and-alerts/alerts/) and best practices for [reducing noise and routing notifications](/product/new-monitors-and-alerts/alerts/best-practices/).
+Learn about [creating alerts](/product/monitors-and-alerts/alerts/) and [notifications](/product/notifications/).
 
 ## Quick Reference
 

diff --git a/docs/organization/integrations/notification-incidents/slack/index.mdx b/docs/organization/integrations/notification-incidents/slack/index.mdx
@@ -41,7 +41,7 @@ Use Slack for notifications and [alerts](#alert-rules) regarding issues, environ
 
 ### Personal Notifications
 
-You can receive personal workflow, deploy, and issue alert notifications from our Slack integration. Manage your [personal notification settings](/product/alerts/notifications/notification-settings/) by navigating to **User Settings > Notifications**.
+You can receive personal workflow, deploy, and issue alert notifications from our Slack integration. Manage your [personal notification settings](/product/notifications/notification-settings/) by navigating to **User Settings > Notifications**.
 
 #### Linking Your Slack and Sentry Accounts
 

diff --git a/docs/platforms/dotnet/common/crons/hangfire/index.mdx b/docs/platforms/dotnet/common/crons/hangfire/index.mdx
@@ -4,7 +4,7 @@ description: "Learn more about how to monitor your Hangfire jobs."
 sidebar_order: 5001
 ---
 
-The .NET SDK provides an integration with [Hangfire](https://www.hangfire.io/) to monitor your jobs by automatically [creating check-ins for them](/product/crons/job-monitoring/). The SDK relies on job filters that are set up when you call `UseSentry`. For example:
+The .NET SDK provides an integration with [Hangfire](https://www.hangfire.io/) to monitor your jobs by automatically [creating check-ins for them](/product/monitors-and-alerts/monitors/crons/job-monitoring/). The SDK relies on job filters that are set up when you call `UseSentry`. For example:
 
 ```csharp
 using Hangfire;

diff --git a/docs/platforms/java/common/crons/troubleshooting.mdx b/docs/platforms/java/common/crons/troubleshooting.mdx
@@ -6,7 +6,7 @@ sidebar_order: 9000
 
 <Expandable title="How do I send an attachment with a check-in (such as a log output)?">
 
-Attachments aren't supported by our Java SDK yet. For now, you can use the [check-in attachments API](/product/crons/getting-started/http/#check-in-attachment-optional).
+Attachments aren't supported by our Java SDK yet. For now, you can use the [check-in attachments API](/product/monitors-and-alerts/monitors/crons/getting-started/http/#check-in-attachment-optional).
 
 </Expandable>
 

diff --git a/docs/platforms/javascript/common/configuration/integrations/denocron.mdx b/docs/platforms/javascript/common/configuration/integrations/denocron.mdx
@@ -13,7 +13,7 @@ This integration only works in the Deno runtime.
 
 _Import name: `Sentry.denoCronIntegration`_
 
-[Sentry Crons](/product/crons/) allows you to monitor the uptime and performance of any scheduled, recurring job in your application.
+[Sentry Crons](/product/monitors-and-alerts/monitors/crons/) allows you to monitor the uptime and performance of any scheduled, recurring job in your application.
 
 The DenoCron integration sets up automatic monitoring for your cron jobs created by [`Deno.cron`](https://docs.deno.com/deploy/kv/manual/cron). It captures check-ins and sends them to Sentry.
 

diff --git a/docs/platforms/javascript/guides/nextjs/manual-setup/pages-router.mdx b/docs/platforms/javascript/guides/nextjs/manual-setup/pages-router.mdx
@@ -432,7 +432,7 @@ Sentry.logger.error("Error occurred");
 
 ## Vercel Cron Jobs (Optional)
 
-Automatically create [Cron Monitors](/product/crons/) in Sentry for your [Vercel cron jobs](https://vercel.com/docs/cron-jobs).
+Automatically create [Cron Monitors](/product/monitors-and-alerts/monitors/crons/) in Sentry for your [Vercel cron jobs](https://vercel.com/docs/cron-jobs).
 
 <SplitLayout>
 

diff --git a/docs/pricing/quotas/legacy-manage-transaction-quota.mdx b/docs/pricing/quotas/legacy-manage-transaction-quota.mdx
@@ -66,7 +66,7 @@ Quotas can only be updated by a Billing or Owner member of your Sentry organizat
 
 </Alert>
 
-Once your performance units volume is approaching or has exceeded the quota, teammates with the "Owner" organization permission level will receive [notification](/product/alerts/notifications/#quota-notifications) emails. You can then choose to [increase](#increasing-quotas) or [decrease](#decreasing-quotas) your quota.
+Once your performance units volume is approaching or has exceeded the quota, teammates with the "Owner" organization permission level will receive [notification](/product/notifications/#quota-notifications) emails. You can then choose to [increase](#increasing-quotas) or [decrease](#decreasing-quotas) your quota.
 
 
 ### Increasing Quotas

diff --git a/docs/pricing/quotas/manage-attachments-quota.mdx b/docs/pricing/quotas/manage-attachments-quota.mdx
@@ -37,7 +37,7 @@ Quotas can only be updated by a Billing or Owner member of your Sentry organizat
 
 </Alert>
 
-Once your attachments volume is approaching or has exceeded the quota, teammates with the "Owner" organization permission level will receive [notification](/product/alerts/notifications/#quota-notifications) emails. You can then choose to [increase](#increasing-quotas) or [decrease](#decreasing-quotas) your quota.
+Once your attachments volume is approaching or has exceeded the quota, teammates with the "Owner" organization permission level will receive [notification](/product/notifications/#quota-notifications) emails. You can then choose to [increase](#increasing-quotas) or [decrease](#decreasing-quotas) your quota.
 
 
 ### Increasing Quotas

diff --git a/docs/pricing/quotas/manage-event-stream-guide.mdx b/docs/pricing/quotas/manage-event-stream-guide.mdx
@@ -63,7 +63,7 @@ Quotas can only be updated by a Billing or Owner member of your Sentry organizat
 
 </Alert>
 
-Once your event volume is approaching or has exceeded the quota, teammates with the "Owner" organization permission level will receive [notification](/product/alerts/notifications/#quota-notifications) emails. You can then choose to [increase](#increasing-quotas) or [decrease](#decreasing-quotas) your quota.
+Once your event volume is approaching or has exceeded the quota, teammates with the "Owner" organization permission level will receive [notification](/product/notifications/#quota-notifications) emails. You can then choose to [increase](#increasing-quotas) or [decrease](#decreasing-quotas) your quota.
 
 If this is your first time exceeding your errors quota and you're on a paid plan, you'll be entered into a one-time grace period. Learn more by reading this [help article](https://sentry.zendesk.com/hc/en-us/articles/23983502355099-What-happens-when-I-run-out-of-event-capacity-and-a-grace-period-is-triggered).
 

diff --git a/docs/pricing/quotas/manage-logs-quota.mdx b/docs/pricing/quotas/manage-logs-quota.mdx
@@ -41,7 +41,7 @@ The "Projects" table on the Stats page breaks down your data by project, so you
 
 Budgets can only be updated by a Billing- or Owner-level member of your Sentry org.
 
-Once your Logs quota is approaching or has exceeded its included amount, teammates with "Owner" org permissions will start receiving [notification](/product/alerts/notifications/#quota-notifications) emails. They'll then be able to choose to increase or decrease the PAYG budget to unlock additional usage.
+Once your Logs quota is approaching or has exceeded its included amount, teammates with "Owner" org permissions will start receiving [notification](/product/notifications/#quota-notifications) emails. They'll then be able to choose to increase or decrease the PAYG budget to unlock additional usage.
 
 ### Increasing Logs Budget
 
@@ -119,7 +119,7 @@ To set up log message filtering:
 Keep track of your Logs quota usage by:
 
 - Checking the [Usage Stats](/product/stats/#usage-stats) page regularly
-- Setting up [quota notifications](/product/alerts/notifications/#quota-notifications)
+- Setting up [quota notifications](/product/notifications/#quota-notifications)
 - Reviewing project-specific usage in the Stats breakdown
 - Monitoring the impact of filtering changes over time
 

diff --git a/docs/pricing/quotas/manage-replay-quota.mdx b/docs/pricing/quotas/manage-replay-quota.mdx
@@ -35,7 +35,7 @@ Quotas can only be updated by a Billing or Owner-level member of your Sentry org
 
 </Alert>
 
-Once your replay volume is approaching or has exceeded its quota, teammates with the "Owner" organization permission level will start receiving [notification](/product/alerts/notifications/#quota-notifications) emails. They'll then be able to choose to [increase](#increasing-quotas) or [decrease](#decreasing-quotas) your quota.
+Once your replay volume is approaching or has exceeded its quota, teammates with the "Owner" organization permission level will start receiving [notification](/product/notifications/#quota-notifications) emails. They'll then be able to choose to [increase](#increasing-quotas) or [decrease](#decreasing-quotas) your quota.
 
 
 ### Increasing Quotas

diff --git a/docs/pricing/quotas/manage-transaction-quota.mdx b/docs/pricing/quotas/manage-transaction-quota.mdx
@@ -44,7 +44,7 @@ Quotas can only be updated by a Billing or Owner member of your Sentry organizat
 
 </Alert>
 
-Once your span unit volume is approaching or has exceeded the quota, teammates with the "Owner" organization permission level will receive [notification](/product/alerts/notifications/#quota-notifications) emails. You can then choose to [increase](#increasing-quotas) or [decrease](#decreasing-quotas) your quota.
+Once your span unit volume is approaching or has exceeded the quota, teammates with the "Owner" organization permission level will receive [notification](/product/notifications/#quota-notifications) emails. You can then choose to [increase](#increasing-quotas) or [decrease](#decreasing-quotas) your quota.
 
 
 ### Increasing Quotas

diff --git a/docs/product/alerts/alert-types.mdx b/docs/product/alerts/alert-types.mdx
@@ -121,7 +121,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 the [uptime check criteria](/product/uptime-monitoring/#uptime-check-criteria). You can customize when alerts are triggered using [thresholds](/product/alerts/create-alerts/uptime-alert-config/#4-thresholds) and define custom success criteria with [verification](/product/alerts/create-alerts/uptime-alert-config/#5-verification) (early access). 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 the [uptime check criteria](/product/monitors-and-alerts/monitors/uptime-monitoring/#uptime-check-criteria). You can customize when alerts are triggered using [thresholds](/product/alerts/create-alerts/uptime-alert-config/#4-thresholds) and define custom success criteria with [verification](/product/alerts/create-alerts/uptime-alert-config/#5-verification) (early access). You'll be able to see the latest uptime check request status ("Up" or "Down") in the "Alert Rules" tab.
 
 ### Alert Details