Skip to content

Commit 285f01a

Browse files
authored
Add note on Data Path Availability metric timing
Added note about Data Path Availability metric delay in Azure Monitor.
1 parent c3af007 commit 285f01a

1 file changed

Lines changed: 3 additions & 0 deletions

File tree

articles/load-balancer/monitor-load-balancer-reference.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -54,6 +54,9 @@ This table includes additional information about metrics from the Microsoft.Netw
5454
| Used SNAT ports | Public load balancer | Standard Load Balancer reports the number of SNAT ports that are utilized per backend instance. |
5555
| Data path availability | Public and internal load balancer | Standard Load Balancer continuously exercises the data path from within a region to the load balancer front end, all the way to the SDN stack that supports your virtual machine. As long as healthy instances remain, the measurement follows the same path as your application's load-balanced traffic. The data path that your customer's use is also validated. The measurement is invisible to your application and doesn't interfere with other operations. |
5656

57+
>[!NOTE]
58+
>Data Path Availability metric may take up to 10 minutes to appear in Azure Monitor metrics after a load balancer is created or updated.
59+
5760
### Global load balancer metrics
5861

5962
This table includes additional information about global metrics from the Microsoft.Network/loadBalancers table:

0 commit comments

Comments
 (0)