Changes per input.

TimShererWithAquent · TimShererWithAquent · commit 3ab3ffe116bc · 2024-09-16T08:46:35.000-07:00
diff --git a/articles/nat-gateway/monitor-nat-gateway-reference.md b/articles/nat-gateway/monitor-nat-gateway-reference.md
@@ -1,7 +1,7 @@
 ---
 title: Monitoring data reference for Azure NAT Gateway
 description: This article contains important reference material you need when you monitor Azure NAT Gateway by using Azure Monitor.
-ms.date: 08/06/2024
+ms.date: 09/16/2024
 ms.custom: horz-monitor
 ms.topic: reference
 author: asudbring
@@ -31,81 +31,7 @@ The following table lists the metrics available for the Microsoft.Network/natgat
 >
 > For information about aggregation types, see [aggregation types](/azure/azure-monitor/essentials/metrics-aggregation-explained#aggregation-types).
 
-## How to use NAT gateway metrics
-
-The following sections detail how to use each NAT gateway metric to monitor, manage, and troubleshoot your NAT gateway resource.
-
-### Bytes
-
-The **Bytes** metric shows you the amount of data going outbound through NAT gateway and returning inbound in response to an outbound connection.
-
-Use this metric to:
-
-- View the amount of data being processed through NAT gateway to connect outbound or return inbound.
-
-### Datapath availability
-
-The datapath availability metric measures the health of the NAT gateway resource over time. This metric indicates if NAT gateway is available for directing outbound traffic to the internet. This metric is a reflection of the health of the Azure infrastructure.
-
-You can use this metric to:
-
-- Monitor the availability of NAT gateway.
-- Investigate the platform where your NAT gateway is deployed and determine if it’s healthy.
-- Isolate whether an event is related to your NAT gateway or to the underlying data plane.
-
-Possible reasons for a drop in data path availability include:
-
-- An infrastructure outage.
-- There aren't healthy VMs available in your NAT gateway configured subnet. For more information, see the [NAT gateway connectivity troubleshooting guide](/azure/nat-gateway/troubleshoot-nat-connectivity).
-
-### Packets
-
-The packets metric shows you the number of data packets passing through NAT gateway. 
-
-Use this metric to:
-  
-- Verify that traffic is passing outbound or returning inbound through NAT gateway.
-- View the amount of traffic going outbound through NAT gateway or returning inbound.
-
-### Dropped packets
-
-The dropped packets metric shows you the number of data packets dropped by NAT gateway when traffic goes outbound or returns inbound in response to an outbound connection.
-
-Use this metric to:
-
-- Check if periods of dropped packets coincide with periods of failed SNAT connections with the [SNAT Connection Count](#snat-connection-count) metric.
-- Help determine if you're experiencing a pattern of failed outbound connections or SNAT port exhaustion.
-
-Possible reasons for dropped packets:
-
-- Outbound connectivity failure can cause packets to drop. Connectivity failure can happen for various reasons. For more information, see the [NAT gateway connectivity troubleshooting guide](/azure/nat-gateway/troubleshoot-nat-connectivity).
-
-### SNAT connection count
-
-The SNAT connection count metric shows you the number of new SNAT connections within a specified time frame. This metric can be filtered by **Attempted** and **Failed** connection states. A failed connection volume greater than zero can indicate SNAT port exhaustion.
-
-Use this metric to:
-
-- Evaluate the health of your outbound connections.
-- Help diagnose if your NAT gateway is experiencing SNAT port exhaustion.
-- Determine if you're experiencing a pattern of failed outbound connections.
-
-### Total SNAT connection count
-
-The **Total SNAT connection count** metric shows you the total number of active SNAT connections passing through NAT gateway.
-
-You can use this metric to:
-
-- Evaluate the volume of connections passing through NAT gateway.
-- Determine if you're nearing the connection limit of NAT gateway.
-- Help assess if you're experiencing a pattern of failed outbound connections.
-
-Possible reasons for failed connections:
-
-- A pattern of failed connections can happen for various reasons. For more information, see the [NAT gateway connectivity troubleshooting guide](/azure/nat-gateway/troubleshoot-nat-connectivity).
-
-> [!NOTE]
-> When NAT gateway is attached to a subnet and public IP address, the Azure platform verifies NAT gateway is healthy by conducting health checks. These health checks appear in NAT gateway's SNAT Connection Count metrics. The amount of health check related connections may vary as the health check service is optimized, but is negligible and doesn’t impact NAT gateway’s ability to connect outbound.
+For more information, see [How to use NAT gateway metrics](nat-metrics.md#how-to-use-nat-gateway-metrics).
 
 [!INCLUDE [horz-monitor-ref-metrics-dimensions-intro](~/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-ref-metrics-dimensions-intro.md)]
 
diff --git a/articles/nat-gateway/monitor-nat-gateway.md b/articles/nat-gateway/monitor-nat-gateway.md
@@ -1,7 +1,7 @@
 ---
 title: Monitor Azure NAT Gateway
 description: Start here to learn how to monitor Azure NAT Gateway by using the available Azure Monitor metrics and alerts.
-ms.date: 08/06/2024
+ms.date: 09/16/2024
 ms.custom: horz-monitor
 ms.topic: conceptual
 author: asudbring
@@ -26,31 +26,7 @@ This diagram shows Azure NAT Gateway for outbound to the internet.
 
 [Azure Monitor Network Insights](../network-watcher/network-insights-overview.md) allows you to visualize your Azure infrastructure setup and to review all metrics for your NAT gateway resource from a preconfigured metrics dashboard. These visual tools help you diagnose and troubleshoot any issues with your NAT gateway resource.
 
-### View the topology of your Azure architectural setup
-
-To view a topological map of your setup in Azure:
-
-1. From your NAT gateway’s resource page, select **Insights** from the **Monitoring** section.
-
-1. On the landing page for **Insights**, there's a topology map of your NAT gateway setup. This map shows the relationship between the different components of your network (subnets, virtual machines, public IP addresses). 
-
-1. To view configuration information, hover over any component in the topology map.
-
-   :::image type="content" source="./media/nat-metrics/nat-insights.png" alt-text="Screenshot of the Insights section of NAT gateway.":::
-
-### View all NAT gateway metrics in a dashboard
-
-The metrics dashboard can be used to better understand the performance and health of your NAT gateway resource. The metrics dashboard shows a view of all metrics for NAT gateway on a single page.  
-
-- All NAT gateway metrics can be viewed in a dashboard when selecting **Show Metrics Pane**.
-
-  :::image type="content" source="./media/nat-metrics/nat-metrics-pane.png" alt-text="Screenshot of the show metrics pane where you can view metrics."::: 
-
-- A full page view of all NAT gateway metrics can be viewed when selecting **View Detailed Metrics**.
-
-  :::image type="content" source="./media/nat-metrics/detailed-metrics.png" alt-text="Screenshot of the view detailed metrics.":::
-
-For more information on what each metric is showing you and how to analyze these metrics, see [How to use NAT gateway metrics](monitor-nat-gateway-reference.md#how-to-use-nat-gateway-metrics).
+For more information on NAT Gateway Insights, see [Insights](nat-metrics.md#insights).
 
 [!INCLUDE [horz-monitor-resource-types](~/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-resource-types.md)]
 For more information about the resource types for Azure NAT Gateway, see [Azure NAT Gateway monitoring data reference](monitor-nat-gateway-reference.md).
@@ -85,57 +61,14 @@ NAT gateway metrics can be found in the following locations in the Azure portal.
 
 [!INCLUDE [horz-monitor-alerts](~/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-alerts.md)]
 
+For guidance on how to configure some common and recommended types of alerts for your NAT gateway, see [Alerts](nat-metrics.md#alerts).
+
 ### Azure NAT Gateway alert rules
 
 You can set alerts for any metric, log entry, or activity log entry listed in the [Azure NAT Gateway monitoring data reference](monitor-nat-gateway-reference.md).
 
-### Alerts for datapath availability degradation
-
-Set up an alert on datapath availability to help you detect issues with the health of NAT gateway.
-
-The recommended guidance is to alert on NAT gateway's datapath availability when it drops below 90% over a 15-minute period. This configuration is indicative of a NAT gateway resource being in a degraded state.
-
-> [!NOTE]
-> Aggregation granularity is the period of time over which the datapath availability is measured to determine if it has dropped below the threshold value. Setting the aggregation granularity to less than 5 minutes may trigger false positive alerts that detect noise in the datapath.
-
-### Alerts for SNAT port exhaustion
-
-Set up an alert on the **SNAT connection count** metric to notify you of connection failures on your NAT gateway. A failed connection volume greater than zero can indicate that you reached the connection limit on your NAT gateway or that you hit SNAT port exhaustion. Investigate further to determine the root cause of these failures.
-
-> [!NOTE]
-> SNAT port exhaustion on your NAT gateway resource is uncommon. If you see SNAT port exhaustion, check if NAT gateway's idle timeout timer is set higher than the default amount of 4 minutes. A long idle timeout timer setting can cause SNAT ports too be in hold down for longer, which results in exhausting SNAT port inventory sooner. You can also scale your NAT gateway with additional public IPs to increase NAT gateway's overall SNAT port inventory. To troubleshoot these kinds of issues, refer to the [NAT gateway connectivity troubleshooting guide](/azure/nat-gateway/troubleshoot-nat-connectivity#snat-exhaustion-due-to-nat-gateway-configuration).
-
-### Alerts for NAT gateway resource health
-
-[Azure Resource Health](/azure/service-health/overview) provides information on the health state of your NAT gateway resource. The resource health of your NAT gateway is evaluated by measuring the datapath availability of your NAT gateway endpoint. You can set up alerts to notify you when the health state of your NAT gateway resource changes. To learn more about NAT gateway resource health and setting up alerts, see:
-
-- [Azure NAT Gateway Resource Health](/azure/nat-gateway/resource-health)
-- [NAT Gateway Resource Health Alerts](/azure/nat-gateway/resource-health#resource-health-alerts)
-- [How to create Resource Health Alerts in the Azure portal](/azure/service-health/resource-health-alert-monitor-guide)
-
 [!INCLUDE [horz-monitor-advisor-recommendations](~/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-advisor-recommendations.md)]
 
-## Metrics FAQ
-
-- What type of metrics are available for NAT gateway?
-
-  The NAT gateway supports [multi-dimensional metrics](/azure/azure-monitor/essentials/data-platform-metrics#multi-dimensional-metrics). You can filter the multi-dimensional metrics by different dimensions to gain greater insight into the provided data. The [SNAT connection count](monitor-nat-gateway-reference.md#snat-connection-count) metric allows you to filter the connections by Attempted and Failed connections, enabling you to distinguish between different types of connections made by the NAT gateway.
-
-  To see which dimensions are available for each NAT gateway metric, see the dimensions column in the [metrics overview table](monitor-nat-gateway-reference.md#metrics).
-
-- How do I store NAT gateway metrics long-term?
-
-  All [platform metrics are stored](/azure/azure-monitor/essentials/data-platform-metrics#retention-of-metrics) for 93 days. If you require long term access to your NAT gateway metrics data, NAT gateway metrics can be retrieved by using the [metrics REST API](/rest/api/monitor/metrics/list). For more information on how to use the API, see the [Azure monitoring REST API walkthrough](/azure/azure-monitor/essentials/rest-api-walkthrough).  
-
-  > [!NOTE]
-  > Diagnostic Settings [doesn’t support the export of multi-dimensional metrics](/azure/azure-monitor/reference/supported-metrics/metrics-index#exporting-platform-metrics-to-other-locations) to another location, such as Azure Storage and Log Analytics.
-  >
-  > To retrieve NAT gateway metrics, use the metrics REST API.
-
-- How do I interpret metrics charts?
-
-  Refer to [troubleshooting metrics charts](/azure/azure-monitor/essentials/metrics-troubleshoot) if you run into issues with creating, customizing, or interpreting charts in Azure metrics explorer.
-
 ## Related content
 
 - See [Azure NAT Gateway monitoring data reference](monitor-nat-gateway-reference.md) for a reference of the metrics, logs, and other important values created for Azure NAT Gateway.
diff --git a/articles/nat-gateway/nat-metrics.md b/articles/nat-gateway/nat-metrics.md
