fix blocking issues

AbbyMSFT · AbbyMSFT · commit bdec24151b70 · 2024-03-07T15:05:48.000+02:00
diff --git a/articles/advisor/advisor-high-availability-recommendations.md b/articles/advisor/advisor-high-availability-recommendations.md
@@ -76,7 +76,7 @@ Virtual machines in an availability set with disks that share either storage acc
 ## Repair invalid log alert rules
 
 Azure Advisor detects log alert rules that have invalid queries specified in their condition section. 
-Azure Monitor log alert rules run queries at specified frequency and fire alerts based on the results. Queries can become invalid over time because of changes in the referenced resources, tables, or commands. Advisor recommends corrections for alert queries to prevent the rules from being automatically disabled and to ensure monitoring coverage. For more information, see [Troubleshooting alert rules](../azure-monitor/alerts/alerts-troubleshoot-log.md#query-used-in-a-log-alert-isnt-valid)
+Azure Monitor log alert rules run queries at specified frequency and fire alerts based on the results. Queries can become invalid over time because of changes in the referenced resources, tables, or commands. Advisor recommends corrections for alert queries to prevent the rules from being automatically disabled and to ensure monitoring coverage. For more information, see [Troubleshooting alert rules](../azure-monitor/alerts/alerts-troubleshoot-log.md)
 
 ## Configure Consistent indexing mode on your Azure Cosmos DB collection
 
diff --git a/articles/azure-monitor/alerts/alerts-metric-multiple-time-series-single-rule.md b/articles/azure-monitor/alerts/alerts-metric-multiple-time-series-single-rule.md
@@ -108,7 +108,7 @@ For this alert rule, two metric time series are being monitored:
 An AND operator is used between the conditions. The alert rule fires an alert when *all* conditions are met. The fired alert resolves if at least one of the conditions is no longer met.
 
 > [!NOTE]
-> There are restrictions when you use dimensions in an alert rule with multiple conditions. For more information, see [Restrictions when using dimensions in a metric alert rule with multiple conditions](alerts-troubleshoot-metric.md#restrictions-when-you-use-dimensions-in-a-metric-alert-rule-with-multiple-conditions).
+> There are restrictions when you use dimensions in an alert rule with multiple conditions. For more information, see [Restrictions when using dimensions in a metric alert rule with multiple conditions](alerts-create-metric-alert-rule.md#restrictions-when-you-use-dimensions-in-a-metric-alert-rule-with-multiple-conditions).
 
 ## Multiple dimensions (multi-dimension)
 
diff --git a/articles/azure-monitor/alerts/alerts-troubleshoot-log.md b/articles/azure-monitor/alerts/alerts-troubleshoot-log.md
@@ -14,7 +14,7 @@ This article describes how to resolve common issues with log search alerts in Az
 You can use log alerts to evaluate resources logs every set frequency by using a [Log Analytics](../logs/log-analytics-tutorial.md) query, and fire an alert that's based on the results. Rules can trigger one or more actions using [Action Groups](./action-groups.md). To learn more about functionality and terminology of log search alerts, see [Log alerts in Azure Monitor](alerts-types.md#log-alerts).
 
 > [!NOTE]
-> This article doesn't consider cases where the Azure portal shows that an alert rule was triggered but a notification isn't received. For such cases, see [Action or notification on my alert did not work as expected](./alerts-troubleshoot.md#action-or-notification-on-my-alert-did-not-work-as-expected).
+> This article doesn't discuss cases where the alert rule was triggered, you can see it in the Azure portal, but the notification was not sent. See [troubleshooting alerts](alerts-troubleshoot.md) for cases like these.
 
 ## A log search alert didn't fire when it should have
 
@@ -59,7 +59,7 @@ Logs are semi-structured data and are inherently more latent than metrics. If yo
 
 Log search alerts work best when you are try to detect specific data in the logs. They are less effective when you are trying to detect lack of data in the logs, like alerting on virtual machine heartbeat. 
 
-1. **Was the the Log search alert rule disabled?**
+1. **Was the the log search alert rule disabled?**
 
 If a log search alert rule query fails to evaluate continuously for a week, Azure Monitor disables it automatically. 
 The following sections list some reasons why Azure Monitor might disable a log search alert rule. Additionally, there's an example of the [Activity log](../../azure-monitor/essentials/activity-log.md) event that is submitted when a rule is disabled.
diff --git a/articles/azure-monitor/alerts/alerts-troubleshoot-metric.md b/articles/azure-monitor/alerts/alerts-troubleshoot-metric.md
@@ -28,7 +28,7 @@ If you believe a metric alert should have fired but it didn't, it isn't listed i
 
 1. **Check if the alert fired but didn't send the notification**
 
-Review the [fired alerts list](https://portal.azure.com/#blade/Microsoft_Azure_Monitoring/AzureMonitoringBrowseBlade/alertsV2) to see if you can locate the fired alert. If you can see the alert in the list but have an issue with some of its actions or notifications, see [Troubleshooting problems in Azure Monitor alerts](./alerts-troubleshoot.md#action-or-notification-on-my-alert-did-not-work-as-expected).
+Review the [fired alerts list](https://portal.azure.com/#blade/Microsoft_Azure_Monitoring/AzureMonitoringBrowseBlade/alertsV2) to see if you can locate the fired alert. If you can see the alert in the list but have an issue with some of its actions or notifications, see [Troubleshooting problems in Azure Monitor alerts](./alerts-troubleshoot.md).
 
 1. **Check if the alert is already active**
 
diff --git a/articles/azure-monitor/alerts/alerts-troubleshoot.md b/articles/azure-monitor/alerts/alerts-troubleshoot.md
@@ -204,7 +204,7 @@ Also, check the payload format (JSON) for [activity log alerts](../alerts/activi
 
    As of log search alerts API version 2021-08-01, search results were removed from alert notification payload. 
    Search results are only available for alert rules created with older API versions (2018-04-16). Creation of new alert rules through the Azure portal will, by default, create the rule with the newer version.
-   Follow [Changes to the log alert rule creation experience](./alerts-manage-alerts-previous-version.md#changes-to-the-log-alert-rule-creation-experience) to learn about the changes and recommended adjustments for using the updated version.
+   Follow [Changes to the log alert rule creation experience](./alerts-manage-alerts-previous-version.md#changes-to-the-log-search-alert-rule-creation-experience) to learn about the changes and recommended adjustments for using the updated version.
 
 ### **The `MetricValue` field contains "null" for resolved log search alert notifications.**
 
@@ -216,11 +216,11 @@ Also, check the payload format (JSON) for [activity log alerts](../alerts/activi
  
 ### Information is missing in an activity log alert
 
-    [Activity log alerts](./alerts-types.md#activity-log-alerts) are alerts that are based on events written to the Azure activity log, such as events about creating, updating, or deleting Azure resources, service health and resource health events, or findings from Azure Advisor and Azure Policy. If you received an alert based on the activity log but some fields that you need are missing or incorrect, first check the events in the activity log itself. If the Azure resource did not write the fields you are looking for in its activity log event, those fields aren't included in the corresponding alert. 
+[Activity log alerts](./alerts-types.md#activity-log-alerts) are alerts that are based on events written to the Azure activity log, such as events about creating, updating, or deleting Azure resources, service health and resource health events, or findings from Azure Advisor and Azure Policy. If you received an alert based on the activity log but some fields that you need are missing or incorrect, first check the events in the activity log itself. If the Azure resource did not write the fields you are looking for in its activity log event, those fields aren't included in the corresponding alert. 
 
 ### The custom properties are missing from email, SMS, or push notifications.
 
-   Custom properties are only passed to the payload for actions, such as webhook, Azure function or logic apps. Custom properties aren't included in for notifications (email/SMS/push).
+Custom properties are only passed to the payload for actions, such as webhook, Azure function or logic apps. Custom properties aren't included in for notifications (email/SMS/push).
 
 ## Alert processing rule isn't working as expected
 
diff --git a/articles/azure-monitor/alerts/log-alert-rule-health.md b/articles/azure-monitor/alerts/log-alert-rule-health.md
@@ -49,7 +49,7 @@ This table describes the possible resource health status values for a log search
 | Resource health status | Description |Recommended steps|
 |---|---|
 |Available|There are no known issues affecting this log search alert rule.|     |
-|Unknown|This log search alert rule is currently disabled or in an unknown state.|[Log alert was disabled](alerts-troubleshoot-log.md#log-search-alert-was-disabled).|
+|Unknown|This log search alert rule is currently disabled or in an unknown state.|[Log alert was disabled](alerts-troubleshoot-log.md).|
 |Unknown reason|This log search alert rule is currently unavailable due to an unknown reason.|Check if the alert rule was recently created. Health status is updated after the rule completes its first evaluation.|
 |Degraded due to unknown reason|This log search alert rule is currently degraded due to an unknown reason.|     |
 |Setting up resource health|Setting up Resource health for this resource.|Check if the alert rule was recently created. Health status is updated after the rule completes its first evaluation.|
diff --git a/articles/backup/metrics-overview.md b/articles/backup/metrics-overview.md
@@ -122,7 +122,7 @@ To configure alerts and notifications on your metrics, follow these steps:
    - To generate an alert on every job failure irrespective of the failure is due to the same underlying cause (stateless behavior), deselect the **Automatically resolve alerts** option in the alert rule.
    - Alternately, to configure the alerts as stateful, select the same checkbox. Therefore, when a metric alert is fired on the scope, another failure won't create a new metric alert. The alert gets auto-resolved if the alert generation condition evaluates to false for three successive evaluation cycles. New alerts are generated if the condition evaluates to true again.
 
-[Learn more about stateful and stateless behavior of Azure Monitor metric alerts](../azure-monitor/alerts/alerts-troubleshoot-metric.md#metric-alert-is-not-triggered-every-time-my-condition-is-met).
+[Learn more about stateful and stateless behavior of Azure Monitor metric alerts](../azure-monitor/alerts/alerts-troubleshoot-metric.md#the-metric-alert-is-not-triggered-every-time-my-condition-is-met).
 
 :::image type="content" source="./media/metrics-overview/auto-resolve-alert-inline.png" alt-text="Screenshot showing the process to configure auto-resolution behavior." lightbox="./media/metrics-overview/auto-resolve-alert-expanded.png":::
 
