diff --git a/docs/cloud/index.mdx b/docs/cloud/index.mdx
index 8c62f613e..9e90562b2 100644
--- a/docs/cloud/index.mdx
+++ b/docs/cloud/index.mdx
@@ -34,9 +34,10 @@ As part of this service you will receive a number of benefits from our team, inc
All of Sourcegraph's features are available on Sourcegraph Cloud instances out-of-the-box, including but not limited to:
- [Cody](/cody)
+- [Deep Search](/deep-search)
- [Server-side Batch Changes](/batch-changes/server-side)
- [Precise code navigation powered by auto-indexing](/code-search/code-navigation/auto_indexing)
-- [Code Monitoring](/code_monitoring/) (including [email delivery](#managed-smtp) of notifications)
+- [Code Monitoring](/code_monitoring/)
- [Code Insights](/code_insights/)
### Access restrictions
diff --git a/docs/code_monitoring/explanations/best_practices.mdx b/docs/code_monitoring/explanations/best_practices.mdx
deleted file mode 100644
index fdbf90473..000000000
--- a/docs/code_monitoring/explanations/best_practices.mdx
+++ /dev/null
@@ -1,19 +0,0 @@
-# Best practices
-
-There are some best practices we recommend when creating code monitors.
-
-## Privacy and visibility
-
-### Do not include confidential information in monitor names
-
-Every code monitor has a name that will be shown wherever the monitor is referenced. In notification actions this name is likely to be the only information about the event, so it’s important for identifying what was triggered, but also has to be “safe” to expose in plain text emails.
-
-### Do not include results when the notification destination is untrusted
-
-Each code monitor action has the ability to include the result contents when sending a notification. This is often convenient because it lets you immediately see which results triggered the notification. However, because the result contents include the code that matched the search query, they may contain sensitive information. Care should be taken to only send result contents if the destination is secure.
-
-For example, if sending the results to a Slack channel, every user that can view that channel will also be able to view the notification messages. The channel should be properly restricted to users who should be able to view that code.
-
-## Scale
-
-Code monitors have been designed to be performant even for large Sourcegraph instances. There are no hard limits on the number of monitors or the volume of code monitored. However, depending on a number of factors such as the number of code monitors, the number of repos monitored, the frequency of commits, and the resources allocated to your instance, it's still possible to hit soft limits. If this happens, your code monitor will continue to work reliably, but it may execute more infrequently.
diff --git a/docs/code_monitoring/explanations/core_concepts.mdx b/docs/code_monitoring/explanations/core_concepts.mdx
deleted file mode 100644
index 507c40870..000000000
--- a/docs/code_monitoring/explanations/core_concepts.mdx
+++ /dev/null
@@ -1,35 +0,0 @@
-# Core concepts
-
-Code monitors allow you to keep track of and get notified about changes in your code. Some use cases for code monitors include getting notifications for potential secrets, anti-patterns, or common typos committed to your codebase.
-
-Code monitors are made up of two main elements: **Triggers** and **Actions**.
-
-## Triggers
-
-A _trigger_ is an event which causes execution of an action. Currently, code monitoring supports one kind of trigger: "When new search results are detected" for a particular search query. When creating a code monitor, users will be asked to specify a query as part of the trigger.
-
-Sourcegraph will run the search query over every new commit for the searched repositories, and when new results for the query are detected, a trigger event is emitted. In response to the trigger event, any _actions_ attached to the code monitor will be executed.
-
-**Query requirements**
-
-A query used in a "When new search results are detected" trigger must be a diff or commit search. In other words, the query must contain `type:commit` or `type:diff`. This allows Sourcegraph to detect new search results periodically.
-
-## Actions
-
-An _action_ is executed in response to a trigger event. Currently, code monitoring supports three different actions:
-
-* Sending a notification email to the owner of the code monitor
-* Sending a Slack message to a preconfigured channel (Beta)
-* Sending a webhook event to an endpoint of your choosing (Beta)
-
-## Current flow
-
-To put it all together, a code monitor has a flow similar to the following:
-
-A user creates a code monitor, which consists of:
-
- * a name for the monitor
- * a trigger, which consists of a search query to run periodically,
- * and an action, which is sending an email, sending a Slack message, or sending a webhook event
-
-Sourcegraph runs the query periodically over new commits. When new results are detected, a notification will be sent with the configured action. It will either contain a link to the search that provided new results, or if the "Include results" setting is enabled, it will include the result contents.
diff --git a/docs/code_monitoring/explanations/index.mdx b/docs/code_monitoring/explanations/index.mdx
deleted file mode 100644
index 4db99693d..000000000
--- a/docs/code_monitoring/explanations/index.mdx
+++ /dev/null
@@ -1,4 +0,0 @@
-# Explanations
-
-* [Core concepts](/code_monitoring/explanations/core_concepts)
-* [Best practices](/code_monitoring/explanations/best_practices)
diff --git a/docs/code_monitoring/how-tos/index.mdx b/docs/code_monitoring/how-tos/index.mdx
deleted file mode 100644
index dafa49f2a..000000000
--- a/docs/code_monitoring/how-tos/index.mdx
+++ /dev/null
@@ -1,5 +0,0 @@
-# How-tos
-
-* [Starting points](/code_monitoring/how-tos/starting_points)
-* [Setting up Slack notifications](/code_monitoring/how-tos/slack)
-* [Setting up Webhook notifications](/code_monitoring/how-tos/webhook)
diff --git a/docs/code_monitoring/how-tos/slack.mdx b/docs/code_monitoring/how-tos/slack.mdx
deleted file mode 100644
index 51fa8d730..000000000
--- a/docs/code_monitoring/how-tos/slack.mdx
+++ /dev/null
@@ -1,29 +0,0 @@
-# Slack notifications for code monitors
-
-You can set up [code monitors](/code_monitoring) to send notifications about new matching search results to Slack channels.
-
-## Requirements
-
-- You must have permission to create apps in your organization's Slack workspace.
-
-## Usage
-
-1. In Sourcegraph, click on the "Code Monitoring" nav item at the top of the page.
-1. Create a new code monitor or edit an existing monitor by clicking on the "Edit" button next to it.
-1. Go through the standard steps for a code monitor (if it's a new one) and select the action **Send Slack message to channel**.
-1. Paste your webhook URL into the "Webhook URL" field. (See "[Creating a Slack incoming webhook URL](#creating-a-slack-incoming-webhook-url)" below for detailed instructions.)
-1. Click on the "Continue" button, and then the "Save" button.
-
-### Creating a Slack incoming webhook URL
-
-1. Go to https://api.slack.com/apps and sign in to your Slack account if necessary.
-1. Click on the "Create an app" button.
-1. Create your app "From scratch".
-1. Give your app a name and select the workplace you want notifications sent to.
-
-1. Once your app is created, click on the "Incoming Webhooks" in the sidebar, under "Features".
-1. Click the toggle button to activate incoming webhooks.
-1. Scroll to the bottom of the page and click on "Add New Webhook to Workspace".
-1. Select the channel you want notifications sent to, then click on the "Allow" button.
-1. Your webhook URL is now created! Click the copy button to copy it to your clipboard.
-
diff --git a/docs/code_monitoring/how-tos/starting_points.mdx b/docs/code_monitoring/how-tos/starting_points.mdx
deleted file mode 100644
index f30bb193b..000000000
--- a/docs/code_monitoring/how-tos/starting_points.mdx
+++ /dev/null
@@ -1,28 +0,0 @@
-# Start monitoring your code
-
-This page lists code monitors that are commonly used and can be used across most codebases.
-
-
-## Watch for consumers of deprecated endpoints
-
-```
-f:\.tsx?$ patterntype:regexp fetch\(['"`]/deprecated-endpoint
-```
-
-If you’re deprecating an API or an endpoint, you may find it useful to set up a code monitor watching for new consumers. As an example, the above query will surface fetch() calls to `/deprecated-endpoint` within TypeScript files. Replace `/deprecated-endpoint` with the actual path of the endpoint being deprecated.
-
-## Get notified when a file changes
-
-```
-patterntype:regexp repo:^github\.com/sourcegraph/sourcegraph$ file:SourcegraphWebApp\.tsx$ type:diff
-```
-
-You may want to get notified when a given file is changed, regardless of the diff contents of the change: the above query will return all changes to the `SourcegraphWebApp.tsx` file on the `github.com/sourcegraph/sourcegraph` repo.
-
-## Get notified when a specific function call is added
-
-```
-repo:^github\.com/sourcegraph/sourcegraph$ type:diff select:commit.diff.added Sprintf
-```
-
-You may want to monitor new additions of a specific function call, for example a deprecated function or a function that introduces a security concern. This query will notify you whenever a new addition of `Sprintf` is added to the `sourcegraph/sourcegraph` repository. This query selects all diff additions marked as "+". If a call of `Sprintf` is both added and removed from a file, this query will still notify due to the addition.
diff --git a/docs/code_monitoring/how-tos/webhook.mdx b/docs/code_monitoring/how-tos/webhook.mdx
deleted file mode 100644
index 55a24b5e1..000000000
--- a/docs/code_monitoring/how-tos/webhook.mdx
+++ /dev/null
@@ -1,63 +0,0 @@
-# Setting up Webhook notifications
-
-Webhook notifications provide a way to execute custom responses to a code monitor notification.
-They are implemented as a POST request to a URL of your choice. The body of the request is defined
-by Sourcegraph, and contains all the information available about the cause of the notification.
-
-## Prerequisites
-
-- You must have a service running that can accept the POST request triggered by the webhook notification
-
-## Creating a webhook receiver
-
-A webhook receiver is a service that can accept an HTTP POST request with the contents of the webhook notification.
-The receiver must be reachable from the Sourcegraph cluster using the URL that is configured below.
-
-The HTTP POST request sent to the receiver will have a JSON-encoded body with the following fields:
-
-- `monitorDescription`: The description of the monitor as configured in the UI
-- `monitorURL`: A link to the monitor configuration page
-- `query`: The query that generated `results`
-- `results`: The list of results that triggered this notification. Contains the following sub-fields
- - `repository`: The name of the repository the commit belongs to
- - `commit`: The commit hash for the matched commit.
- - `diff`: The matching diff in unified diff format. Only set if the result is a diff match.
- - `matchedDiffRanges`: The character ranges of `diff` that matched `query`. Only set if the result is a diff match.
- - `message`: The matching commit message. Only set if the result is a commit match.
- - `matchedMessageRanges`: The character ranges of `message` that matched `query`. Only set if the result is a commit match.
-
-Example payload:
-```json
-{
- "monitorDescription": "My test monitor",
- "monitorURL": "https://sourcegraph.com/code-monitoring/Q29kZU1vbml0b3I6NDI=?utm_source=",
- "query": "repo:camdentest -file:id_rsa.pub BEGIN",
- "results": [
- {
- "repository": "github.com/test/test",
- "commit": "7815187511872asbasdfgasd",
- "diff": "file1.go file2.go\n@ -97,5 +97,5 @ func Test() {\n leading context\n+matched added\n-matched removed\n trailing context\n",
- "matchedDiffRanges": [
- [ 66, 73 ],
- [ 91, 98 ]
- ]
- },
- {
- "repository": "github.com/test/test",
- "commit": "7815187511872asbasdfgasd",
- "message": "summary line\n\nsample\ncommit\nmessage\n",
- "matchedMessageRanges": [
- [ 15, 19 ]
- ]
- }
- ]
-}
-```
-
-## Configuring a code monitor to send Webhook notifications
-
-1. In Sourcegraph, click on the "Code Monitoring" nav item at the top of the page.
-1. Create a new code monitor or edit an existing monitor by clicking on the "Edit" button next to it.
-1. Go through the standard configuration steps for a code monitor and select action "Call a webhook".
-1. Paste your webhook URL into the "Webhook URL" field.
-1. Click on the "Continue" button, and then the "Save" button.
diff --git a/docs/code_monitoring/index.mdx b/docs/code_monitoring/index.mdx
index 829e05826..162a93184 100644
--- a/docs/code_monitoring/index.mdx
+++ b/docs/code_monitoring/index.mdx
@@ -7,17 +7,183 @@
-Keep on top of events in your codebase
+Keep on top of events in your codebase. Watch your code with code monitors and trigger actions to run automatically in response to events.
-Watch your code with code monitors and trigger actions to run automatically in response to events.
+Code monitors allow you to keep track of and get notified about changes in your code. Some use cases for code monitors include getting notifications for potential secrets, anti-patterns, or common typos committed to your codebase.
-## Getting started
+Here are some starting points for your first code monitor:
-
-
-
-
+**Watch for consumers of deprecated endpoints**
-## Questions & Feedback
+```
+f:\.tsx?$ patterntype:regexp fetch\(['"`]/deprecated-endpoint
+```
-We want to hear your feedback! [Share your thoughts](mailto:feedback@sourcegraph.com)
+If you’re deprecating an API or an endpoint, you may find it useful to set up a code monitor watching for new consumers. As an example, the above query will surface fetch() calls to `/deprecated-endpoint` within TypeScript files. Replace `/deprecated-endpoint` with the actual path of the endpoint being deprecated.
+
+**Get notified when a file changes**
+
+```
+patterntype:regexp repo:^github\.com/sourcegraph/sourcegraph$ file:SourcegraphWebApp\.tsx$ type:diff
+```
+
+You may want to get notified when a given file is changed, regardless of the diff contents of the change: the above query will return all changes to the `SourcegraphWebApp.tsx` file on the `github.com/sourcegraph/sourcegraph` repo.
+
+**Get notified when a specific function call is added**
+
+```
+repo:^github\.com/sourcegraph/sourcegraph$ type:diff select:commit.diff.added Sprintf
+```
+
+You may want to monitor new additions of a specific function call, for example a deprecated function or a function that introduces a security concern. This query will notify you whenever a new addition of `Sprintf` is added to the `sourcegraph/sourcegraph` repository. This query selects all diff additions marked as "+". If a call of `Sprintf` is both added and removed from a file, this query will still notify due to the addition.
+
+Code monitors are made up of two main elements: **Triggers** and **Actions**.
+
+## Triggers
+
+A _trigger_ is an event which causes execution of an action. Currently, code monitoring supports one kind of trigger: "When new search results are detected" for a particular search query. When creating a code monitor, users will be asked to specify a query as part of the trigger.
+
+Sourcegraph will run the search query over every new commit for the searched repositories, and when new results for the query are detected, a trigger event is emitted. In response to the trigger event, any _actions_ attached to the code monitor will be executed.
+
+A query used in a "When new search results are detected" trigger must be a `type:commit` or `type:diff` search. This allows Sourcegraph to detect new search results periodically.
+
+## Actions
+
+An _action_ is executed in response to a trigger event. Currently, code monitoring supports three different actions:
+
+### Sending a notification email to the owner of the code monitor
+
+Prerequisite: Ensure [email notifications](/admin/observability/alerting#email) are configured in site configuration.
+
+1. Click the _Code monitoring_ menu item at the top right of your page.
+2. Click the _Create new code monitor_ button at the top right of the page.
+3. Fill out the _Name_ input with: "TODOs".
+4. Under the _Trigger_ section, click _When there are new search results_.
+5. In the _Search query_ input, enter the following search query:
+`TODO type:diff patternType:keyword`.
+(Note that `type:` and `patternType:` are required as part of the search query for code monitoring.)
+1. You can click _Preview results_ to see all previous additions or removals of TODO to your codebase.
+2. Back in the code monitor form, click _Continue_.
+3. Click _Send email notifications_ under the _Actions_ section. You can use "Send test email" to verify you can properly receive notifications and to lean more about the format.
+4. Click _Done_.
+5. Click _Create code monitor_.
+
+You should now see the TODO code monitor on the page, and you will receive email notifications whenever the trigger fires.
+
+### Sending a Slack message to a channel
+
+You can set up code monitors to send notifications about new matching search results to Slack channels.
+
+#### Usage
+
+1. In Sourcegraph, click on the "Code Monitoring" nav item at the top of the page.
+1. Create a new code monitor or edit an existing monitor by clicking on the "Edit" button next to it.
+1. Under actions, select **Send Slack message to channel**.
+1. Paste your webhook URL into the "Webhook URL" field. (See "[Creating a Slack incoming webhook URL](#creating-a-slack-incoming-webhook-url)" below for detailed instructions.)
+1. Click on the "Continue" button, and then the "Save" button.
+
+##### Creating a Slack incoming webhook URL
+
+1. You must have permission to create apps in your organization's Slack workspace.
+1. Go to https://api.slack.com/apps and sign in to your Slack account if necessary.
+1. Click on the "Create an app" button.
+1. Create your app "From scratch".
+1. Give your app a name and select the workplace you want notifications sent to.
+
+1. Once your app is created, click on the "Incoming Webhooks" in the sidebar, under "Features".
+1. Click the toggle button to activate incoming webhooks.
+1. Scroll to the bottom of the page and click on "Add New Webhook to Workspace".
+1. Select the channel you want notifications sent to, then click on the "Allow" button.
+1. Your webhook URL is now created! Click the copy button to copy it to your clipboard.
+
+
+### Sending a webhook event to an endpoint of your choosing
+
+Webhook notifications provide a way to execute custom responses to a code monitor notification.
+They are implemented as a POST request to a URL of your choice. The body of the request is defined
+by Sourcegraph, and contains all the information available about the cause of the notification.
+
+#### Prerequisites
+
+- You must have a service running that can accept the POST request triggered by the webhook notification
+
+#### Creating a webhook receiver
+
+A webhook receiver is a service that can accept an HTTP POST request with the contents of the webhook notification.
+The receiver must be reachable from the Sourcegraph cluster using the URL that is configured below.
+
+The HTTP POST request sent to the receiver will have a JSON-encoded body with the following fields:
+
+- `monitorDescription`: The description of the monitor as configured in the UI
+- `monitorURL`: A link to the monitor configuration page
+- `query`: The query that generated `results`
+- `results`: The list of results that triggered this notification. Contains the following sub-fields
+ - `repository`: The name of the repository the commit belongs to
+ - `commit`: The commit hash for the matched commit.
+ - `diff`: The matching diff in unified diff format. Only set if the result is a diff match.
+ - `matchedDiffRanges`: The character ranges of `diff` that matched `query`. Only set if the result is a diff match.
+ - `message`: The matching commit message. Only set if the result is a commit match.
+ - `matchedMessageRanges`: The character ranges of `message` that matched `query`. Only set if the result is a commit match.
+
+
+
+```json
+{
+ "monitorDescription": "My test monitor",
+ "monitorURL": "https://sourcegraph.com/code-monitoring/Q29kZU1vbml0b3I6NDI=?utm_source=",
+ "query": "repo:camdentest -file:id_rsa.pub BEGIN",
+ "results": [
+ {
+ "repository": "github.com/test/test",
+ "commit": "7815187511872asbasdfgasd",
+ "diff": "file1.go file2.go\n@ -97,5 +97,5 @ func Test() {\n leading context\n+matched added\n-matched removed\n trailing context\n",
+ "matchedDiffRanges": [
+ [ 66, 73 ],
+ [ 91, 98 ]
+ ]
+ },
+ {
+ "repository": "github.com/test/test",
+ "commit": "7815187511872asbasdfgasd",
+ "message": "summary line\n\nsample\ncommit\nmessage\n",
+ "matchedMessageRanges": [
+ [ 15, 19 ]
+ ]
+ }
+ ]
+}
+```
+
+
+
+### Current flow
+
+To put it all together, a code monitor has a flow similar to the following:
+
+A user creates a code monitor, which consists of:
+
+- a name for the monitor
+- a trigger, which consists of a search query to run periodically,
+- and an action, which is sending an email, sending a Slack message, or sending a webhook event
+
+Sourcegraph runs the query periodically over new commits. When new results are detected, a notification will be sent with the configured action. It will either contain a link to the search that provided new results, or if the "Include results" setting is enabled, it will include the result contents.
+
+## Best practices
+
+There are some best practices we recommend when creating code monitors.
+
+### Privacy and visibility
+
+#### Do not include confidential information in monitor names
+
+Every code monitor has a name that will be shown wherever the monitor is referenced. In notification actions this name is likely to be the only information about the event, so it’s important for identifying what was triggered, but also has to be “safe” to expose in plain text emails.
+
+#### Do not include results when the notification destination is untrusted
+
+Each code monitor action has the ability to include the result contents when sending a notification. This is often convenient because it lets you immediately see which results triggered the notification. However, because the result contents include the code that matched the search query, they may contain sensitive information. Care should be taken to only send result contents if the destination is secure.
+
+For example, if sending the results to a Slack channel, every user that can view that channel will also be able to view the notification messages. The channel should be properly restricted to users who should be able to view that code.
+
+### Scale
+
+Code monitors have been designed to be performant even for large Sourcegraph instances. There are no hard limits on the number of monitors or the volume of code monitored. However, depending on a number of factors such as the number of code monitors, the number of repos monitored, the frequency of commits, and the resources allocated to your instance, it's still possible to hit soft limits. If this happens, your code monitor will continue to work reliably, but it may execute more infrequently.
diff --git a/docs/code_monitoring/quickstart.mdx b/docs/code_monitoring/quickstart.mdx
deleted file mode 100644
index e2e80ab61..000000000
--- a/docs/code_monitoring/quickstart.mdx
+++ /dev/null
@@ -1,37 +0,0 @@
-# Quickstart for code monitoring
-
-## Introduction
-
-In this tutorial, we will create a new code monitor that monitors new appearances of the word "TODO" in your codebase.
-
-## Creating a code monitor
-
-Prerequisite: Ensure [email notifications](/admin/observability/alerting#email) are configured in site configuration.
-
-1. On your Sourcegraph instance, click the **Code monitoring** menu item at the top right of your page. Alternatively, go to `https://sourcegraph.example.com/code-monitoring` (where sourcegraph.example.com represents your unique Sourcegraph url).
-2. Click the **Create new code monitor** button at the top right of the page.
-3. Fill out the **Name** input with: "TODOs".
-4. Under the **Trigger** section, click **When there are new search results**.
-5. In the **Search query** input, enter the following search query:
-`TODO type:diff patternType:keyword`.
-(Note that `type:` and `patternType:` are required as part of the search query for code monitoring.)
-1. You can click **Preview results** to see all previous additions or removals of TODO to your codebase.
-2. Back in the code monitor form, click **Continue**.
-3. Click **Send email notifications** under the **Actions** section.
-4. Click **Done**.
-5. Click **Create code monitor**.
-
-You should now be on `https://sourcegraph.example.com/code-monitoring`, and be able to see the TODO code monitor on the page.
-
-## Sending a test email notification
-
-If you want to preview the email notification alerting you of a new result with TODO, follow these steps:
-
-1. In the **Send email notifications** action, click "Send test email".
-1. Within a few minutes, you should receive a test email from Sourcegraph with a preview of the email notification.
-
-If you want to test receiving an email with a real new result, follow these steps:
-
-1. In any repository that's on your Sourcegraph instance (for purposes of this tutorial, we recommend a dummy or test repo that's not used), add `TODO` to any file.
-1. Commit the change, and push it to your code host.
-1. Within a few minutes, you should see an email from Sourcegraph with a link to the new result you just pushed.
diff --git a/src/data/navigation.ts b/src/data/navigation.ts
index 4dc7dc8c7..b0fcd9134 100644
--- a/src/data/navigation.ts
+++ b/src/data/navigation.ts
@@ -406,14 +406,6 @@ export const navigation: NavigationItem[] = [
{
title: 'Code Monitoring',
href: '/code_monitoring',
- sections: [
- { title: 'Quickstart', href: '/code_monitoring/quickstart' },
- {
- title: 'Explanations',
- href: '/code_monitoring/explanations'
- },
- { title: 'How-to Guides', href: '/code_monitoring/how-tos' }
- ]
},
{
title: 'Code Ownership',
diff --git a/src/data/redirects.ts b/src/data/redirects.ts
index 0b67be29f..3ba2e5e18 100644
--- a/src/data/redirects.ts
+++ b/src/data/redirects.ts
@@ -6881,6 +6881,48 @@ const redirectsData = [
destination: 'https://sourcegraph.com/pricing',
permanent: true
},
+
+ // Code monitoring redirects - merged pages into consolidated index
+ {
+ source: '/code_monitoring/explanations/best_practices',
+ destination: '/code_monitoring',
+ permanent: true
+ },
+ {
+ source: '/code_monitoring/explanations/core_concepts',
+ destination: '/code_monitoring',
+ permanent: true
+ },
+ {
+ source: '/code_monitoring/explanations',
+ destination: '/code_monitoring',
+ permanent: true
+ },
+ {
+ source: '/code_monitoring/how-tos',
+ destination: '/code_monitoring',
+ permanent: true
+ },
+ {
+ source: '/code_monitoring/how-tos/slack',
+ destination: '/code_monitoring',
+ permanent: true
+ },
+ {
+ source: '/code_monitoring/how-tos/starting_points',
+ destination: '/code_monitoring',
+ permanent: true
+ },
+ {
+ source: '/code_monitoring/how-tos/webhook',
+ destination: '/code_monitoring',
+ permanent: true
+ },
+ {
+ source: '/code_monitoring/quickstart',
+ destination: '/code_monitoring',
+ permanent: true
+ },
];
const updatedRedirectsData = redirectsData.map(redirect => {