Merge pull request #262615 from EdB-MSFT/custom-metrics-refresh

custom overview

Author: Stacyrch140

articles/azure-monitor/containers/container-insights-custom-metrics.md

@@ -81,10 +81,7 @@ This process assigns the *Monitoring Metrics Publisher* role to the cluster's se
 
 ### Prerequisites
 
-Before you update your cluster:
-
-- See the supported regions for custom metrics at [Supported regions](../essentials/metrics-custom-overview.md#supported-regions).
-- Confirm that you're a member of the [Owner](../../role-based-access-control/built-in-roles.md#owner) role on the AKS cluster resource to enable collection of custom performance metrics for nodes and pods. This requirement doesn't apply to Azure Arc-enabled Kubernetes clusters.
+Before you update your cluster, confirm that you're a member of the [Owner](../../role-based-access-control/built-in-roles.md#owner) role on the AKS cluster resource to enable collection of custom performance metrics for nodes and pods. This requirement doesn't apply to Azure Arc-enabled Kubernetes clusters.
 
 ### Enablement options
 Use one of the following methods to enable custom metrics for either a single cluster or all clusters in your subscription.

articles/azure-monitor/containers/container-insights-metric-alerts.md

@@ -110,9 +110,8 @@ The configuration change can take a few minutes to finish before it takes effect
 
 ### Prerequisites
 
-  - You might need to enable collection of custom metrics for your cluster. See [Metrics collected by Container insights](container-insights-custom-metrics.md).
-  - See the supported regions for custom metrics at [Supported regions](../essentials/metrics-custom-overview.md#supported-regions).
-
+You might need to enable collection of custom metrics for your cluster. See [Metrics collected by Container insights](container-insights-custom-metrics.md).
+  
 ### Enable and configure metric alert rules
 
 #### [Azure portal](#tab/azure-portal)

articles/azure-monitor/containers/container-insights-region-mapping.md

@@ -40,11 +40,6 @@ Supported AKS regions are listed in [Products available by region](https://azure
 |WestCentralUS<sup>1</sup>|EastUS |
 
 
-
-## Custom metrics supported regions
-
-Collecting metrics from Azure Kubernetes Services (AKS) clusters nodes and pods are supported for publishing as custom metrics only in the following [Azure regions](../essentials/metrics-custom-overview.md#supported-regions).
-
 ## Next steps
 
 To begin monitoring your AKS cluster, review [How to enable the Container insights](container-insights-onboard.md) to understand the requirements and available methods to enable monitoring.  

articles/azure-monitor/containers/container-insights-troubleshoot.md

@@ -112,8 +112,6 @@ To view the non-AKS cluster in Container insights, read access is required on th
 
 ## Metrics aren't being collected
 
-1. Verify that the cluster is in a [supported region for custom metrics](../essentials/metrics-custom-overview.md#supported-regions).
-
 1. Verify that the **Monitoring Metrics Publisher** role assignment exists by using the following CLI command:
 
     ``` azurecli

articles/azure-monitor/essentials/app-insights-metrics.md

@@ -15,7 +15,7 @@ Application Insights log-based metrics let you analyze the health of your monito
 * [Log-based metrics](../app/pre-aggregated-metrics-log-metrics.md#log-based-metrics) behind the scene are translated into [Kusto queries](/azure/kusto/query/) from stored events.
 * [Standard metrics](../app/pre-aggregated-metrics-log-metrics.md#pre-aggregated-metrics) are stored as pre-aggregated time series.
 
-Since *standard metrics* are pre-aggregated during collection, they have better performance at query time. This makes them a better choice for dashboarding and in real-time alerting. The *log-based metrics* have more dimensions, which makes them the superior option for data analysis and ad-hoc diagnostics. Use the [namespace selector](./metrics-custom-overview.md#namespace) to switch between log-based and standard metrics in [metrics explorer](./analyze-metrics.md).
+Since *standard metrics* are pre-aggregated during collection, they have better performance at query time. This makes them a better choice for dashboarding and in real-time alerting. The *log-based metrics* have more dimensions, which makes them the superior option for data analysis and ad-hoc diagnostics. Use the [namespace selector](./metrics-store-custom-rest-api.md#namespace) to switch between log-based and standard metrics in [metrics explorer](./analyze-metrics.md).
 
 ## Interpret and use queries from this article
 

articles/azure-monitor/essentials/collect-custom-metrics-guestos-resource-manager-vm.md

@@ -22,7 +22,6 @@ If you're new to ARM templates, learn about [template deployments](../../azure-r
 
 - Your subscription must be registered with [Microsoft.Insights](../../azure-resource-manager/management/resource-providers-and-types.md).
 - You need to have either [Azure PowerShell](/powershell/azure) or [Azure Cloud Shell](../../cloud-shell/overview.md) installed.
-- Your VM resource must be in a [region that supports custom metrics](./metrics-custom-overview.md#supported-regions).
 
 ## Set up Azure Monitor as a data sink
 The Azure Diagnostics extension uses a feature called *data sinks* to route metrics and logs to different locations. The following steps show how to use an ARM template and PowerShell to deploy a VM by using the new Azure Monitor data sink.

articles/azure-monitor/essentials/collect-custom-metrics-guestos-resource-manager-vmss.md

@@ -23,8 +23,6 @@ If you're new to Resource Manager templates, learn about [template deployments](
 
 - You need to have [Azure PowerShell](/powershell/azure) installed, or you can use [Azure Cloud Shell](../../cloud-shell/overview.md). 
 
-- Your VM resource must be in a [region that supports custom metrics](./metrics-custom-overview.md#supported-regions).
-
 ## Set up Azure Monitor as a data sink 
 The Azure Diagnostics extension uses a feature called **data sinks** to route metrics and logs to different locations. The following steps show how to use a Resource Manager template and PowerShell to deploy a VM by using the new Azure Monitor data sink. 
 
@@ -252,9 +250,6 @@ To deploy the Resource Manager template, use Azure PowerShell:
     New-AzResourceGroup -Name "VMSSWADtestGrp" -Location "<Azure Region>"
    ```
 
-   > [!NOTE]  
-   > Remember to use an Azure region that's enabled for custom metrics. Remember to use an [Azure region that's enabled for custom metrics](./metrics-custom-overview.md#supported-regions).
-
 1. Run the following commands to deploy the VM:
 
    > [!NOTE]

articles/azure-monitor/essentials/collect-custom-metrics-guestos-vm-classic.md

@@ -27,8 +27,6 @@ The process that's outlined in this article only works on classic virtual machin
 
 - You need to have either [Azure PowerShell](/powershell/azure) or [Azure Cloud Shell](../../cloud-shell/overview.md) installed.
 
-- Your VM resource must be in a [region that supports custom metrics](./metrics-custom-overview.md#supported-regions).
-
 ## Create a classic virtual machine and storage account
 
 1. Create a classic VM by using the Azure portal.

articles/azure-monitor/essentials/collect-custom-metrics-guestos-vm-cloud-service-classic.md

@@ -25,8 +25,6 @@ The process that's outlined in this article works only for performance counters
 
 - You need to have either [Azure PowerShell](/powershell/azure) or [Azure Cloud Shell](../../cloud-shell/overview.md) installed.
 
-- Your Cloud Service must be in a [region that supports custom metrics](./metrics-custom-overview.md#supported-regions).
-
 ## Provision a cloud service and storage account 
 
 1. Create and deploy a classic cloud service. A sample classic Cloud Services application and deployment can be found at [Get started with Azure Cloud Services and ASP.NET](../../cloud-services/cloud-services-dotnet-get-started.md).