Documentation for Monitors and Alerts

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](/product/monitors/crons/getting-started/cli/), 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:

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/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

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/crons/job-monitoring/). The SDK relies on job filters that are set up when you call `UseSentry`. For example:
 
 ```csharp
 using Hangfire;

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/crons/getting-started/http/#check-in-attachment-optional).
 
 </Expandable>
 

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/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.
 

docs/platforms/javascript/guides/nextjs/manual-setup.mdx

@@ -492,7 +492,7 @@ module.exports = withSentryConfig(nextConfig, {
 
 ## Step 6: Instrument Vercel Cron Jobs (Optional)
 
-You can automatically create [Cron Monitors](/product/crons/) in Sentry if you have configured [Vercel cron jobs](https://vercel.com/docs/cron-jobs).
+You can automatically create [Cron Monitors](/product/monitors/crons/) in Sentry if you have configured [Vercel cron jobs](https://vercel.com/docs/cron-jobs).
 
 Update `withSentryConfig` in your `next.config.(js|mjs)` file with the following option:
 

docs/product/alerts/best-practices.mdx

@@ -7,9 +7,7 @@ description: "Learn best practices for creating alerts."
 
 Alerts should notify you when there's an important problem with your application. But they shouldn't be too noisy, because that can lead to alert fatigue. The following best practices will help you create relevant alerts that notify the right people — that is, the people equipped to fix the problem.
 
-There are two types of alerts: [issue alerts](/product/alerts/alert-types/#issue-alerts) and [metric alerts](/product/alerts/alert-types/#metric-alerts). Most of our alerting best practices are specific to issue alerts, however, the [alert conditions best practices](#alert-conditions-best-practices) apply to both issue and metric alerts.
-
-## Issue Alerts Best Practices
+## Best Practices
 
 An issue alert is triggered when an individual issue meets some criteria. These criteria (or "triggers") can be based on state-changes or frequency. The best practices that follow cover alerts based on state and frequency changes, as well as reducing noise, and effective routing.