You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/load-balancer/load-balancer-standard-diagnostics.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -126,18 +126,18 @@ To get SNAT connection statistics:
126
126
127
127
#### How do I check my SNAT port usage and allocation?
128
128
129
-
The SNAT usage metric demonstrates how many unique flows are establish between a source and backend VMs or VMSSes. By comparing this with the SNAT allocation metric, you can determine if your service is experiencing or at risk of SNAT exhaustion and resulting outbound flow failure.
129
+
The SNAT Usage metric indicates how many unique flows are established between an internet source and a backend VM or VMSS that is behind a load balancer and does not have a pubic IP address. By comparing this to the SNAT Allocation metric, you can determine if your service is experiencing or at risk of SNAT exhaustion and resulting outbound flow failure.
130
130
131
131
If your metrics indicate risk of [outbound flow](https://aka.ms/lboutbound) failure, reference the article and take steps to mitigate this to ensure service health.
132
132
133
133
To get SNAT usage and allocation:
134
134
1. Set the time aggregation of the graph to 1 minute to ensure desired data is displayed.
135
135
1. Select **SNAT Usage** and/or **SNAT Allocation** as the metric type and **Average** as the aggregation
136
-
* By default this will be the average number of SNAT ports allocated to or used by each backend VMs or VMSSes, corresponding to all frontend public IPs mapped to the Load Balancer, aggregated over TCP and UDP.
136
+
* By default this is the average number of SNAT ports allocated to or used by each backend VMs or VMSSes, corresponding to all frontend public IPs mapped to the Load Balancer, aggregated over TCP and UDP.
137
137
* To view total SNAT ports used by or allocated for the load balancer use metric aggregation **Sum**
138
138
1. Filter to a specific **Protocol Type**, a set of **Backend IPs**, and/or **Frontend IPs**.
139
139
1. To monitor health per backend or frontend instance, apply splitting.
140
-
* Note this only allows for a single metric to be displayed at a time.
140
+
* Note splitting only allows for a single metric to be displayed at a time.
141
141
1. For example, to monitor SNAT usage for TCP flows per machine, aggregate by **Average**, split by **Backend IPs** and filter by **Protocol Type**.
142
142
143
143

0 commit comments