Merge pull request #79797 from snehithm/patch-6

Update metric mapping

Author: PRMerger8

articles/azure-monitor/platform/alerts-understand-migration.md

@@ -17,7 +17,7 @@ This article explains how the voluntary migration tool works. It also describes
 > [!NOTE]
 > Due to delay in roll-out of migration tool, the retirement date for classic alerts migration has been [extended to August 31st, 2019](https://azure.microsoft.com/updates/azure-monitor-classic-alerts-retirement-date-extended-to-august-31st-2019/) from the originally announced date of June 30th, 2019.
 
-## Which classic alert rules can be migrated?
+## Which classic alert rules cannot be migrated?
 
 Although the tool can migrate almost all classic alert rules, there are some exceptions. The following alert rules won't be migrated by using the tool (or during the automatic migration in September 2019):
 
@@ -27,6 +27,8 @@ Although the tool can migrate almost all classic alert rules, there are some exc
 
 If your subscription has any such classic rules, you must migrate them manually. Because we can't provide an automatic migration, any existing, classic metric alerts of these types will continue to work until June 2020. This extension gives you time to move over to new alerts. However, no new classic alerts can be created after August 2019.
 
+Besides the above listed exceptions, if your classic alert rules are invalid i.e. they are on [deprecated metrics](#classic- alert-rules-on-deprecated-metrics) or resources that have been deleted, they will not be migrated during voluntary migration. Any such invalid classic alert rules will be deleted when automatic migration happens. 
+
 ### Guest metrics on virtual machines
 
 Before you can create new metric alerts on guest metrics, the guest metrics must be sent to the Azure Monitor custom metrics store. Follow these instructions to enable the Azure Monitor sink in diagnostic settings:
@@ -55,6 +57,20 @@ Classic alert rules on Percent metrics must be migrated based on [the mapping be
 
 Classic alert rules on AnonymousThrottlingError, SASThrottlingError and ThrottlingError must be split into two new alerts because there is no combined metric that provides the same functionality. Thresholds will need to be adapted appropriately.
 
+### Classic alert rules on deprecated metrics
+
+These are classic alert rules on metrics which were supported for a while before they were eventually deprecated. A small percentage of customer might have invalid classic alert rules on such metrics. Since these alert rules are invalid, they won't be migrated. 
+
+| Resource type| Deprecated metric(s) |
+|-------------|----------------- |
+| Microsoft.DBforMySQL/servers | compute_consumption_percent, compute_limit |
+| Microsoft.DBforPostgreSQL/servers | compute_consumption_percent, compute_limit |
+| Microsoft.Network/publicIPAddresses | defaultddostriggerrate |
+| Microsoft.SQL/servers/databases | service_level_objective, storage_limit, storage_used, throttling, dtu_consumption_percent, storage_used |
+| Microsoft.Web/hostingEnvironments/multirolepools | averagememoryworkingset |
+| Microsoft.Web/hostingEnvironments/workerpools | bytesreceived, httpqueuelength |
+
+
 ## Rollout phases
 
 The migration tool is rolling out in phases to customers that use classic alert rules. Subscription owners will receive an email when the subscription is ready to be migrated by using the tool.

articles/azure-monitor/platform/alerts-using-migration-tool.md

@@ -32,7 +32,7 @@ The migration process converts classic alert rules to new, equivalent alert rule
 
 - Both the notification payload format and the APIs to create and manage new alert rules are different from those of the classic alert rules because they support more features. [Learn how to prepare for the migration](alerts-prepare-migration.md).
 
-- Some classic alert rules cannot be migrated by using the tool. [Learn which rules cannot be migrated and what to do with them](alerts-understand-migration.md#which-classic-alert-rules-can-be-migrated).
+- Some classic alert rules cannot be migrated by using the tool. [Learn which rules cannot be migrated and what to do with them](alerts-understand-migration.md#which-classic-alert-rules-cannot-be-migrated).
 
     > [!NOTE]
     > The migration process won't impact the evaluation of your classic alert rules. They'll continue to run and send alerts until they're migrated and the new alert rules take effect.

articles/azure-monitor/platform/monitoring-classic-retirement.md

@@ -61,7 +61,7 @@ At the end of August 2019, in Azure Monitor:
 - Any alert rules that continue to exist in Alerts (classic) beyond August 2019 will continue to execute and fire notifications, but not be available for modification.
 - Starting September 2019, alert rules in classic monitoring & alerting which can be migrated, will be automatically moved by Microsoft to their equivalent in the new Azure monitor platform in phases spanning few weeks. The process will be seamless without any downtime and customers will have no loss in monitoring coverage.
 - Alert rules migrated to the new alerts platform will provide monitoring coverage as before but will fire notification with new payloads. Any email address, webhook endpoint, or logic app link associated with classic alert rule will be carried forward when migrated, but may not behave correctly as alert payload will be different in the new platform.
-- Some [classic alert rules that cannot be automatically migrated](alerts-understand-migration.md#which-classic-alert-rules-can-be-migrated) and require manual action from users will continue to run until June 2020.
+- Some [classic alert rules that cannot be automatically migrated](alerts-understand-migration.md#which-classic-alert-rules-cannot-be-migrated) and require manual action from users will continue to run until June 2020.
 
 > [!IMPORTANT]
 > Microsoft Azure Monitor has rolled out in phases [tool to voluntarily migrate](alerts-using-migration-tool.md) their classic alert rules on to the new platform soon. And run it by force for all classic alert rules that still exist and can be migrated, starting September 2019. Customers will need to ensure automation consuming classic alert rule payload is adapted to handle the new payload from [Unified Metrics and Alerts in Application Insights](#unified-metrics-and-alerts-in-application-insights) or [Unified Metrics and Alerts for other Azure resources](#unified-metrics-and-alerts-for-other-azure-resources), post-migration of the classic alert rules. For more information, see [prepare for classic alert rule migration](alerts-prepare-migration.md)