![]() Make sure the correct load balancer resource is selected. To get the data path availability for your standard load balancer resources: Don’t confuse this metric with the health probe status ("Backend instance availability"). Isolate whether an event is related to your service or the underlying data plane. Determine if your guest OS or application instance is healthy. Investigate the platform where your service is deployed and determine if it's healthy. Monitor the external availability of your service. The metric is a reflection of the health of the Azure infrastructure. The metric for data path availability describes the health within the region of the data path to the compute host where your VMs are located. Common diagnostic scenarios and recommended views Is the data path up and available for my load balancer frontend? Expand These metrics can be written to a storage account by adding a diagnostic setting for the 'All Metrics' category. Recommendation: When analyzing metric aggregation type Sum and Count, we recommend using a time aggregation value that is greater than one minute.įigure: Metric for data path availability for a standard load balancer Retrieve multi-dimensional metrics programmatically via APIsįor API guidance for retrieving multi-dimensional metric definitions and values, see Azure Monitoring REST API walkthrough. If time aggregation is set to five minutes and metric aggregation type Sum is used for metrics such as SNAT allocation, your graph will display five times the total allocated SNAT ports. Time aggregation is important when interpreting certain metrics as data is sampled once per minute. This is expected as the Azure Load Balancer algorithm is based on flowsĪ standard load balancer reports the packets processed per front end. You may notice that the bytes aren’t distributed equally across the backend instances. The counters can be used to troubleshoot and understand the health of your outbound flows.Ī standard load balancer reports the number of SNAT ports allocated per backend instanceĪ standard load balancer reports the number of SNAT ports that are utilized per backend instance.Ī standard load balancer reports the data processed per front end. Counters for successful and failed outbound SNAT flows are reported. ![]() This metric can give an indication of how heavily your application is relying on SNAT for outbound originated flows. Source Network Address Translation (SNAT) connection countĪ standard load balancer reports the number of outbound flows that are masqueraded to the Public IP address frontend. The metric reports the number of TCP SYN packets that were received. To better troubleshoot your TCP protocol scenarios, you can make use of SYN packets counters to understand how many TCP connection attempts are made. Flows and their handshakes are always between the source and the VM instance. You can see how load balancer views the health of your application, as indicated by your health probe configuration.Ī standard load balancer doesn’t terminate Transmission Control Protocol (TCP) connections or interact with TCP or User Data-gram Packet (UDP) flows. This metric provides an aggregate or per-endpoint filtered view of each instance endpoint in the load balancer pool. The measurement is invisible to your application and doesn’t interfere with other operations.Ī standard load balancer uses a distributed health-probing service that monitors your application endpoint's health according to your configuration settings. As long as healthy instances remain, the measurement follows the same path as your application's load-balanced traffic. The various load balancer configurations provide the following metrics: MetricĪ standard load balancer continuously uses the data path from within a region to the load balancer frontend, to the network that supports your VM. Multi-dimensional metricsĪzure Load Balancer provides multi-dimensional metrics via the Azure Metrics in the Azure portal, and it helps you get real-time diagnostic insights into your load balancer resources. ![]() This article provides a quick tour of these capabilities, and it offers ways to use them for a standard load balancer. This automatic check informs you of the current availability of your load balancer resource. Resource health: The Resource Health status of your load balancer is available in the Resource health page under Monitor. You can monitor, manage, and troubleshoot your standard load balancer resources. Multi-dimensional metrics and alerts: Provides multi-dimensional diagnostic capabilities through Azure Monitor for standard load balancer configurations. Azure Load Balancer exposes the following diagnostic capabilities:
0 Comments
Leave a Reply. |