Merge pull request #267556 from AbbyMSFT/troubleshoot

Alerts troubleshooting updates

Author: American-Dipper

articles/advisor/advisor-high-availability-recommendations.md

@@ -12,7 +12,7 @@ Azure Advisor helps you ensure and improve the continuity of your business-criti
 
 ## Check the version of your Check Point network virtual appliance image
 
-Advisor can identify whether your virtual machine is running a version of the Check Point image that has been known to lose network connectivity during platform servicing operations. The Advisor recommendation will help you upgrade to a newer version of the image that addresses this problem. This check will ensure business continuity through better network connectivity.
+Advisor can identify whether your virtual machine is running a version of the Check Point image that has been known to lose network connectivity during platform servicing operations. The Advisor recommendation helps you upgrade to a newer version of the image that addresses this problem. This check ensures business continuity through better network connectivity.
 
 ## Ensure application gateway fault tolerance
 
@@ -56,7 +56,7 @@ Azure Advisor checks for any VPN gateways that use a Basic SKU and recommends th
 - Higher stability and availability.
 
 ## Ensure reliable outbound connectivity with VNet NAT
-Using default outbound connecitivty provided by a Standard Load Balancer or other Azure resources is not recommended for production workloads as this causes connection failures (also called SNAT port exhaustion). The recommended approach is using a VNet NAT which will prevent any failures of connectivity in this regard. NAT can scale seamlessly to ensure your application is never out ports. [Learn more about VNet NAT](../virtual-network/nat-gateway/nat-overview.md).
+Using default outbound connectivity provided by a Standard Load Balancer or other Azure resources is not recommended for production workloads as this causes connection failures (also called SNAT port exhaustion). The recommended approach is using a VNet NAT which will prevent any failures of connectivity in this regard. NAT can scale seamlessly to ensure your application is never out ports. [Learn more about VNet NAT](../virtual-network/nat-gateway/nat-overview.md).
 
 ## Ensure virtual machine fault tolerance (temporarily disabled)
 
@@ -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
 
@@ -110,10 +110,10 @@ Starting July 1, 2020, you won't be able to create new Spark clusters by using S
 Virtual machines that don't have replication enabled to another region aren't resilient to regional outages. Replicating virtual machines reduces any adverse business impact during Azure region outages. Advisor detects VMs on which replication isn't enabled and recommends enabling it. When you enable replication, if there's an outage, you can quickly bring up your virtual machines in a remote Azure region. [Learn more about virtual machine replication.](../site-recovery/azure-to-azure-quickstart.md)
 
 ## Upgrade to the latest version of the Azure Connected Machine agent
-The [Azure Connected Machine agent](../azure-arc/servers/manage-agent.md) is updated regularly with bug fixes, stability enhancements, and new functionality. We have identified resources which are not working on the latest version of machine agent and this Advisor recommendation will suggest you to upgrade your agent to the latest version for the best Azure Arc experience.
+The [Azure Connected Machine agent](../azure-arc/servers/manage-agent.md) is updated regularly with bug fixes, stability enhancements, and new functionality. We have identified resources which are not working on the latest version of machine agent and this Advisor recommendation suggests that you to upgrade your agent to the latest version for the best Azure Arc experience.
 
 ## Do not override hostname to ensure website integrity
-Advisor recommend to try avoid overriding the hostname when configuring Application Gateway. Having a different domain on the frontend of Application Gateway than the one which is used to access the backend can potentially lead to cookies or redirect URLs being broken. Note that this might not be the case in all situations and that certain categories of backends (like REST API's) in general are less sensitive to this. Please make sure the backend is able to deal with this or update the Application Gateway configuration so the hostname does not need to be overwritten towards the backend. When used with App Service, attach a custom domain name to the Web App and avoid use of the `*.azurewebsites.net` host name towards the backend. [Learn more about custom domain](../application-gateway/troubleshoot-app-service-redirection-app-service-url.md).
+Advisor recommends that you try avoid overriding the hostname when configuring Application Gateway. Having a different domain on the frontend of Application Gateway than the one which is used to access the backend can potentially lead to cookies or redirect URLs being broken. Note that this might not be the case in all situations and that certain categories of backends (like REST APIs) in general are less sensitive to this. Please make sure the backend is able to deal with this or update the Application Gateway configuration so the hostname does not need to be overwritten towards the backend. When used with App Service, attach a custom domain name to the Web App and avoid use of the `*.azurewebsites.net` host name towards the backend. [Learn more about custom domain](../application-gateway/troubleshoot-app-service-redirection-app-service-url.md).
 
 ## Next steps
 

articles/azure-monitor/alerts/alerts-create-log-alert-rule.md

@@ -57,9 +57,10 @@ Alerts triggered by these alert rules contain a payload that uses the [common al
     For sample log search alert queries that query ARG or ADX, see [Log search alert query samples](./alerts-log-alert-query-samples.md)
 
    For limitations:
-   * [Cross-service query limitations](https://learn.microsoft.com/azure/azure-monitor/logs/azure-monitor-data-explorer-proxy#limitations)
-   * [Combine Azure Resource Graph tables with a Log Analytics workspace](https://learn.microsoft.com/azure/azure-monitor/logs/azure-monitor-data-explorer-proxy#combine-azure-resource-graph-tables-with-a-log-analytics-workspace) limitations
-   * Not suppprted in Gov clouds
+   * [Cross-service query limitations](../logs/azure-monitor-data-explorer-proxy.md#limitations)
+   * [Combine Azure Resource Graph tables with a Log Analytics workspace](../logs/azure-monitor-data-explorer-proxy.md#combine-azure-resource-graph-tables-with-a-log-analytics-workspace)
+   * Not supported in government clouds
+
 1. Select **Run** to run the alert.
 1. The **Preview** section shows you the query results. When you're finished editing your query, select **Continue Editing Alert**.
 1. The **Condition** tab opens populated with your log query. By default, the rule counts the number of results in the last five minutes. If the system detects summarized query results, the rule is automatically updated with that information.

articles/azure-monitor/alerts/alerts-create-metric-alert-rule.md

@@ -4,7 +4,7 @@ description: This article shows you how to create a new metric alert rule.
 author: AbbyMSFT
 ms.author: abbyweisberg
 ms.topic: how-to
-ms.date: 11/27/2023
+ms.date: 03/07/2024
 ms.reviewer: harelbr
 ---
 
@@ -16,6 +16,14 @@ You create an alert rule by combining the resources to be monitored, the monitor
 
 Alerts triggered by these alert rules contain a payload that uses the [common alert schema](alerts-common-schema.md).
 
+## Permissions to create metric alert rules
+
+To create a metric alert rule, you must have the following permissions:
+
+  - Read permission on the target resource of the alert rule.
+  - Write permission on the resource group in which the alert rule is created. If you're creating the alert rule from the Azure portal, the alert rule is created by default in the same resource group in which the target resource resides.
+  - Read permission on any action group associated to the alert rule, if applicable.
+
 [!INCLUDE [alerts-wizard-access](../includes/alerts-wizard-access.md)]
 
 [!INCLUDE [alerts-wizard-scope](../includes/alerts-wizard-scope.md)]
@@ -126,5 +134,41 @@ Alerts triggered by these alert rules contain a payload that uses the [common al
 [!INCLUDE [alerts-wizard-finish](../includes/alerts-wizard-finish.md)]
 
 
+## Naming restrictions for metric alert rules
+
+Consider the following restrictions for metric alert rule names:
+
+- Metric alert rule names can't be changed (renamed) after they're created.
+- Metric alert rule names must be unique within a resource group.
+- Metric alert rule names can't contain the following characters: * # & + : < > ? @ % { } \ /
+- Metric alert rule names can't end with a space or a period.
+- The combined resource group name and alert rule name can't exceed 252 characters.
+
+> [!NOTE]
+> If the alert rule name contains characters that aren't alphabetic or numeric, for example, spaces, punctuation marks, or symbols, these characters might be URL-encoded when retrieved by certain clients.
+
+## Restrictions when you use dimensions in a metric alert rule with multiple conditions
+
+Metric alerts support alerting on multi-dimensional metrics and support defining multiple conditions, up to five conditions per alert rule.
+
+Consider the following constraints when you use dimensions in an alert rule that contains multiple conditions:
+
+- You can only select one value per dimension within each condition.
+- You can't use the option to **Select all current and future values**. Select the asterisk (\*).
+- When metrics that are configured in different conditions support the same dimension, a configured dimension value must be explicitly set in the same way for all those metrics in the relevant conditions.
+For example:
+    - Consider a metric alert rule that's defined on a storage account and monitors two conditions:
+        * Total **Transactions** > 5
+        * Average **SuccessE2ELatency** > 250 ms
+    - You want to update the first condition and only monitor transactions where the **ApiName** dimension equals `"GetBlob"`.
+    - Because both the **Transactions** and **SuccessE2ELatency** metrics support an **ApiName** dimension, you'll need to update both conditions, and have them specify the **ApiName** dimension with a `"GetBlob"` value.
+
+
+## Considerations when creating an alert rule that contains multiple criteria
+   - You can only select one value per dimension within each criterion.
+   - You can't use an asterisk (\*) as a dimension value.
+   - When metrics that are configured in different criteria support the same dimension, a configured dimension value must be explicitly set in the same way for all those metrics. For a Resource Manager template example, see [Create a metric alert with a Resource Manager template](./alerts-metric-create-templates.md#template-for-a-static-threshold-metric-alert-that-monitors-multiple-criteria).
+
+
 ## Next steps
  [View and manage your alert instances](alerts-manage-alert-instances.md)

articles/azure-monitor/alerts/alerts-logic-apps.md

@@ -4,7 +4,7 @@ description: Learn how to create a logic app to process Azure Monitor alerts.
 author: EdB-MSFT
 ms.author: abbyweisberg
 ms.topic: conceptual
-ms.date: 02/09/2023
+ms.date: 03/10/2024
 ms.reviewer: edbaynash
 
 # Customer intent: As an administrator, I want to create a logic app that's triggered by an alert so that I can send emails or Teams messages when an alert is fired.

articles/azure-monitor/alerts/alerts-manage-alert-rules.md

@@ -3,7 +3,7 @@ title: Manage your alert rules
 description: Manage your alert rules in the Azure portal, or using the CLI or PowerShell.
 author: AbbyMSFT
 ms.author: abbyweisberg
-ms.topic: conceptual
+ms.topic: how-to
 ms.custom: devx-track-azurecli
 ms.date: 01/14/2024
 ms.reviewer: harelbr
@@ -120,6 +120,33 @@ Metric alert rules have these dedicated PowerShell cmdlets:
 - [Update](/rest/api/monitor/metricalerts/update): Update a metric alert rule.
 - [Delete](/rest/api/monitor/metricalerts/delete): Delete a metric alert rule.
 
+## Delete metric alert rules defined on a deleted resource
+
+When you delete an Azure resource, associated metric alert rules aren't deleted automatically. To delete alert rules associated with a resource that's been deleted:
+
+1. Open the resource group in which the deleted resource was defined.
+1. In the list that displays the resources, select the **Show hidden types** checkbox.
+1. Filter the list by Type == **microsoft.insights/metricalerts**.
+1. Select the relevant alert rules and select **Delete**.
+
+## Check the number of metric alert rules in use
+
+To check the current number of metric alert rules in use, follow the next steps.
+### From the Azure portal
+
+   1. Open the **Alerts** screen and select **Manage alert rules**.
+   1. Filter to the relevant subscription by using the **Subscription** dropdown box.
+   1. Make sure *not* to filter to a specific resource group, resource type, or resource.
+   1. In the **Signal type** dropdown box, select **Metrics**.
+   1. Verify that the **Status** dropdown box is set to **Enabled**.
+   1. The total number of metric alert rules are displayed above the alert rules list.
+    
+### Using the API
+
+   - **PowerShell**: [Get-AzMetricAlertRuleV2](/powershell/module/az.monitor/get-azmetricalertrulev2)
+   - **REST API**: [List by subscription](/rest/api/monitor/metricalerts/listbysubscription)
+   - **Azure CLI**: [az monitor metrics alert list](/cli/azure/monitor/metrics/alert#az-monitor-metrics-alert-list)
+
 ## Manage log search alert rules using the CLI
 
 This section describes how to manage log search alerts using the cross-platform [Azure CLI](/cli/azure/get-started-with-azure-cli). The following examples use [Azure Cloud Shell](../../cloud-shell/overview.md). 
@@ -157,6 +184,22 @@ A 201 response is returned on successful creation. 200 is returned on successful
 Log search alert rules have this dedicated PowerShell cmdlet:
 - [New-AzScheduledQueryRule](/powershell/module/az.monitor/new-azscheduledqueryrule): Creates a new log search alert rule or updates an existing log search alert rule.
 
+## Check the number of log alert rules in use
+
+### In the Azure portal
+1. On the Alerts screen in Azure Monitor, select **Alert rules**.
+1. In the **Subscription** dropdown control, filter to the subscription you want. (Make sure you don't filter to a specific resource group, resource type, or resource.)
+1. In the **Signal type** dropdown control, select **Log Search**.
+1. Verify that the **Status** dropdown control is set to **Enabled**.
+
+The total number of log search alert rules is displayed above the rules list.
+
+### Using the API
+
+- PowerShell - [Get-AzScheduledQueryRule](/powershell/module/az.monitor/get-azscheduledqueryrule)
+- CLI: [az monitor scheduled-query list](/cli/azure/monitor/scheduled-query#az-monitor-scheduled-query-list)
+- REST API - [List by subscription](/rest/api/monitor/scheduledqueryrule-2021-08-01/scheduled-query-rules/list-by-subscription)
+
 ## Manage activity log alert rules using PowerShell
 
 Activity log alerts have these dedicated PowerShell cmdlets:
@@ -167,6 +210,7 @@ Activity log alerts have these dedicated PowerShell cmdlets:
 - [Disable-AzActivityLogAlert](/powershell/module/az.monitor/disable-azactivitylogalert): Disables an existing activity log alert and sets its tags.
 - [Remove-AzActivityLogAlert](/powershell/module/az.monitor/remove-azactivitylogalert): Removes an activity log alert.
 
+
 ## Next steps
 
 - [Learn about Azure Monitor alerts](./alerts-overview.md)

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)