Merge pull request #264373 from thisisanniefang/patch-66

prmerger-automator[bot] · web-flow · commit d3c50f00a242 · 2024-01-26T22:28:14.000Z
Update load-balancer-standard-diagnostics.md
diff --git a/articles/load-balancer/load-balancer-standard-diagnostics.md b/articles/load-balancer/load-balancer-standard-diagnostics.md
@@ -38,7 +38,7 @@ The various load balancer configurations provide the following metrics:
 | Packet count |  Public and internal load balancer | A standard load balancer reports the packets processed per front end.| Sum |
 
   >[!NOTE]
-  >When using distributing traffic from an internal load balancer through an NVA or firewall syn packet, byte count, and packet count metrics are not be available and will show as zero. 
+  >Bandwidth-related metrics such as SYN packet, byte count, and packet count will not capture any traffic to an internal load balancer via a UDR (eg. from an NVA or firewall). 
   >
   >Max and min aggregations are not available for the SYN count, packet count, SNAT connection count, and byte count metrics.
   >Count aggregation is not recommended for Data path availability and health probe status. Use average instead for best represented health data.

Original file line number	Diff line number	Diff line change
`@@ -38,7 +38,7 @@ The various load balancer configurations provide the following metrics:`
`38`	`38`	`\| Packet count \| Public and internal load balancer \| A standard load balancer reports the packets processed per front end.\| Sum \|`
`39`	`39`
`40`	`40`	`>[!NOTE]`
`41`		`- >When using distributing traffic from an internal load balancer through an NVA or firewall syn packet, byte count, and packet count metrics are not be available and will show as zero.`
	`41`	`+ >Bandwidth-related metrics such as SYN packet, byte count, and packet count will not capture any traffic to an internal load balancer via a UDR (eg. from an NVA or firewall).`
`42`	`42`	`>`
`43`	`43`	`>Max and min aggregations are not available for the SYN count, packet count, SNAT connection count, and byte count metrics.`
`44`	`44`	`>Count aggregation is not recommended for Data path availability and health probe status. Use average instead for best represented health data.`