Skip to content

Commit cb43d70

Browse files
authored
grammar
1 parent 3f2947f commit cb43d70

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/load-balancer/load-balancer-standard-diagnostics.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -126,18 +126,18 @@ To get SNAT connection statistics:
126126

127127
#### How do I check my SNAT port usage and allocation?
128128

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.
130130

131131
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.
132132

133133
To get SNAT usage and allocation:
134134
1. Set the time aggregation of the graph to 1 minute to ensure desired data is displayed.
135135
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.
137137
* To view total SNAT ports used by or allocated for the load balancer use metric aggregation **Sum**
138138
1. Filter to a specific **Protocol Type**, a set of **Backend IPs**, and/or **Frontend IPs**.
139139
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.
141141
1. For example, to monitor SNAT usage for TCP flows per machine, aggregate by **Average**, split by **Backend IPs** and filter by **Protocol Type**.
142142

143143
![SNAT allocation and usage](./media/load-balancer-standard-diagnostics/snat-usage-and-allocation.png)

0 commit comments

Comments
 (0)