getsentry · sfanahata · Mar 9, 2026 · Feb 19, 2026 · Feb 19, 2026 · Mar 6, 2026
diff --git a/docs/organization/integrations/issue-tracking/height/index.mdx b/docs/organization/integrations/issue-tracking/height/index.mdx
@@ -32,7 +32,7 @@ Issue tracking allows you to create Height tasks from within [sentry.io](https:/
 
 ### Automatically
 
-To configure issue management automatically, create an [issue alert](/product/alerts/alert-types/#issue-alerts) or a [metric alert](/product/alerts/alert-types/#metric-alerts). When selecting the [action](/product/alerts/create-alerts/issue-alert-config/#then-conditions-actions), choose "Notify Integration" and then "Height" for issue alerts, or select "Height" from the action dropdown for metric alerts:
+To configure issue management automatically, create an [issue alert](/product/alerts/alert-types/#issue-alerts) or a [metric alert](/product/alerts/alert-types/#metric-alerts). Metric alerts create issues in Sentry when triggered, so you can send those issues to Height the same way as issue alerts. When selecting the [action](/product/alerts/create-alerts/issue-alert-config/#then-conditions-actions), choose "Notify Integration" and then "Height" for issue alerts, or select "Height" from the action dropdown for metric alerts:
 
 ![Height metric alert rule action settings](./img/height-rule.png)
 

diff --git a/docs/organization/integrations/issue-tracking/linear/index.mdx b/docs/organization/integrations/issue-tracking/linear/index.mdx
@@ -33,7 +33,7 @@ Issue tracking allows you to create Linear issues from within Sentry, and link S
 
 ### Automatically
 
-To configure issue management automatically, create an [issue alert](/product/alerts/alert-types/#issue-alerts) or a [metric alert](/product/alerts/alert-types/#metric-alerts). When selecting the [action](/product/alerts/create-alerts/issue-alert-config/#then-conditions-actions), choose "Notify Integration" and then "Linear" for issue alerts, or select "Linear" from the action dropdown for metric alerts:
+To configure issue management automatically, create an [issue alert](/product/alerts/alert-types/#issue-alerts) or a [metric alert](/product/alerts/alert-types/#metric-alerts). Metric alerts create issues in Sentry when triggered, so you can send those issues to Linear the same way as issue alerts. When selecting the [action](/product/alerts/create-alerts/issue-alert-config/#then-conditions-actions), choose "Notify Integration" and then "Linear" for issue alerts, or select "Linear" from the action dropdown for metric alerts:
 
 ![Create Linear issue as metric alert rule action](./img/linear-rule.png)
 

diff --git a/docs/organization/integrations/notification-incidents/pagerduty/index.mdx b/docs/organization/integrations/notification-incidents/pagerduty/index.mdx
@@ -51,7 +51,7 @@ In [issue alerts](/product/alerts/alert-types/#issue-alerts), select "Send a Pag
 
 ![PagerDuty alert rule action](./img/pd_alert_rule.png)
 
-In [metric alerts](/product/alerts/alert-types/#metric-alerts), select the PagerDuty option in the dropdown that corresponds to your account and the select your service. You can also select a custom severity for the alert, or leave it blank to use the default severity level that Sentry provides for incident statuses ("critical" for critical status and "warning" for warning status).
+In [metric alerts](/product/alerts/alert-types/#metric-alerts), select the PagerDuty option in the dropdown that corresponds to your account and then select your service. You can also select a custom severity for the alert, or leave it blank to use the default severity level that Sentry provides for incident statuses ("critical" for critical status and "warning" for warning status).
 
 ![PagerDuty metric alert rule action](./img/pd_metric_alert_rule.png)
 

diff --git a/docs/organization/integrations/notification-incidents/slack/index.mdx b/docs/organization/integrations/notification-incidents/slack/index.mdx
@@ -67,7 +67,7 @@ Once you receive a Slack notification for an issue alert, you can use the "Resol
 
 #### Metric Alerts
 
-In [metric alerts](/product/alerts/alert-types/#metric-alerts), select the Slack option in the dropdown that corresponds to your workspace and the select your channel:
+In [metric alerts](/product/alerts/alert-types/#metric-alerts), select the Slack option in the dropdown that corresponds to your workspace and then select your channel:
 
 ![Slack metric alert action](./img/slack_metric_alert.png)
 

diff --git a/docs/product/alerts/alert-types.mdx b/docs/product/alerts/alert-types.mdx
@@ -37,7 +37,7 @@ The **Alert Details** page also includes a list of issues that triggered the ale
 
 ## Metric Alerts
 
-Metric alerts tell you when a [metric](/product/insights/overview/metrics/) crosses a threshold set by you, like a spike in the number of errors in a project, or a change in a performance metric, such as [transaction duration](/product/insights/overview/metrics/#latency), [Apdex](/product/insights/overview/metrics/#apdex), [failure rate](/product/insights/overview/metrics/#failure-rate), or [throughput](/product/insights/overview/metrics/#throughput-total-tpm-tps). You can use [dynamic alerts](/product/alerts/create-alerts/metric-alert-config/#dynamic-alerts) to let Sentry define the threshold for you.
+Metric alerts tell you when a [metric](/product/insights/overview/metrics/) crosses a threshold set by you, like a spike in the number of errors in a project, or a change in a metric, such as [transaction duration](/product/insights/overview/metrics/#latency), [Apdex](/product/insights/overview/metrics/#apdex), [failure rate](/product/insights/overview/metrics/#failure-rate), or [throughput](/product/insights/overview/metrics/#throughput-total-tpm-tps). You can use [dynamic alerts](/product/alerts/create-alerts/metric-alert-config/#dynamic-alerts) to let Sentry define the threshold for you.
 
 Metric alerts monitor macro-level metrics for both error and transaction events. A metric takes a set of events and computes an aggregate value using a function, such as `count()` or `avg()`, applied to the event properties over a period of time. When you create a metric alert, you can filter events by attributes and <PlatformLink to="/enriching-events/tags/">tags</PlatformLink>, which is particularly useful for aggregating across events that aren't grouped into single issues. Sentry allows a maximum of 1000 metric alerts for an organization.
 
@@ -49,6 +49,10 @@ Metric alerts may include [archived issues](/product/issues/states-triage/#archi
 
 These alerts use _Critical_ and _Warning_ triggers to measure severity. An alert’s current status is the highest severity trigger that is active, which can be one of three values: Warning, Critical, or Resolved. Sentry notifies you whenever an alert's status changes.
 
+### Metric Alerts create Issues 
+
+When you create a Metric Alert, Sentry will automatically create an [Issue](/product/issues/) for you. This issue will be associated with the metric alert. You can see related Issues on the Alert Details page. You can find your alerts [here](https://sentry.io/orgredirect/organizations/:orgslug/issues/alerts/rules/).
+
 When you create an alert, all the displayed alert types (except “Issues”) may be used to create a metric alert. You can create metric alerts for Errors, Sessions (Crash Rate Alerts), and Performance:
 
 ### Errors
@@ -109,7 +113,7 @@ Application performance alerts can help you pinpoint and identify specific probl
 
 ### Alert Details
 
-The **Alert Details** page shows you the history of a metric alert rule for the last 24 hours by default, though can modify the time period using the "Display" dropdown. When an alert is triggered, clicking the notification you receive takes you to this page, which displays the period when the alert was active. The page also includes details such as the alert rule conditions, the current status of the alert, and a summary of how much time the alert spent in each state (Critical, Warning, or Resolved).
+The **Alert Details** page shows you the history of a metric alert rule for the last 24 hours by default, though you can modify the time period using the "Display" dropdown. When an alert is triggered, clicking the notification you receive takes you to this page, which displays the period when the alert was active. The page also includes details such as the alert rule conditions, the current status of the alert, and a summary of how much time the alert spent in each state (Critical, Warning, or Resolved).
 
 ![Alert details illustrates a graph showing the performance of a transaction over time.](./img/alert-details-example.png)
 

diff --git a/docs/product/alerts/best-practices.mdx b/docs/product/alerts/best-practices.mdx
@@ -7,7 +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.
+There are two types of alerts: [issue alerts](/product/alerts/alert-types/#issue-alerts) and [metric alerts](/product/alerts/alert-types/#metric-alerts). Metric alerts also create issues when triggered, so you can triage and assign them like issue 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
 

diff --git a/docs/product/alerts/create-alerts/index.mdx b/docs/product/alerts/create-alerts/index.mdx
@@ -16,7 +16,7 @@ The minimum role required to create alerts is member. Sentry users with manager
 To create alerts:
 
 1. Navigate to **Alerts** and click "Create Alert Rule".
-1. Choose what you want to be alerted about. Selecting “Issues” creates an [issue alert](/product/alerts/alert-types/#issue-alerts), selecting “Uptime Monitor” creates an [uptime alert](/product/alerts/alert-types/#uptime-alerts), while selecting any other option creates a [metric alert](/product/alerts/alert-types/#metric-alerts).
+1. Choose what you want to be alerted about. Selecting “Issues” creates an [issue alert](/product/alerts/alert-types/#issue-alerts), selecting “Uptime Monitor” creates an [uptime alert](/product/alerts/alert-types/#uptime-alerts), while selecting any other option creates a [metric alert](/product/alerts/alert-types/#metric-alerts). Metric alerts also create issues when triggered.
    ![Choice between alerts about Errors, Sessions, Performance, or a Custom Metric](./img/create-new-alert-rule.png)
 
 1. Click "Set Conditions".

diff --git a/docs/product/alerts/create-alerts/metric-alert-config.mdx b/docs/product/alerts/create-alerts/metric-alert-config.mdx
@@ -5,7 +5,7 @@ description: Learn more about the options for configuring a metric alert.
 og_image: /og-images/product-alerts-create-alerts-metric-alert-config.png
 ---
 
-Sentry provides several configuration options to create a metric alert based on your organization's needs.
+Sentry provides several configuration options to create a metric alert based on your organization's needs. When a metric alert is triggered, Sentry automatically creates an [issue](/product/issues/) that you can view, triage, and assign on the [Alert Details](/product/alerts/alert-types/#metric-alerts) page.
 
 ## Metric (Type + Function + Time Interval)
 

diff --git a/docs/product/alerts/index.mdx b/docs/product/alerts/index.mdx
@@ -39,13 +39,21 @@ Create alerts to monitor specific metrics, such as:
 - Crash free session or user rate for monitoring release health
 - Custom metrics
 
+### Metric Alerts create Issues 
+
+When you create a Metric Alert, Sentry will automatically create an [Issue](/product/issues/) for you. This issue will be associated with the metric alert. You can see related Issues on the Alert Details page. You can find your alerts [here](https://sentry.io/orgredirect/organizations/:orgslug/issues/alerts/rules/).
+
 You can find a full list of available metric alerts in [Metric Alerts](/product/alerts/alert-types/#metric-alerts).
 
 ## Uptime Monitoring Alerts
 
 [Uptime alerts](/product/uptime-monitoring/) are triggered when an uptime HTTP 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). Use uptime alerts to make sure a specific URL is constantly available, even during periods of low or no traffic.
 
+## Cron Monitor Alerts
+
+[Cron monitor alerts](/product/crons/) are triggered when a scheduled, recurring job misses a check-in, exceeds its maximum runtime, or reports a failure. You can view and manage cron monitors from the **Alerts** page by filtering by the "Cron Monitors" alert type. Use cron monitor alerts to ensure critical jobs run on schedule and complete successfully. Set up monitoring and configure alerts in [Cron Monitoring](/product/crons/getting-started/).
+
 ## Creating Alerts
 
 When you create a new project in [sentry.io](https://sentry.io), you can select a default issue alert. However, you can also [create your own alerts](/product/alerts/create-alerts/) to suit your team’s needs, using these [alert best practices](/product/alerts/best-practices/) as a guide.