Skip to content

Commit 40fe43c

Browse files
TimShererWithAquentTimShererWithAquent
committed
Update per templates.
1 parent e6d7b7a commit 40fe43c

File tree

3 files changed

+123
-168
lines changed

3 files changed

+123
-168
lines changed

‎articles/load-balancer/TOC.yml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -132,10 +132,8 @@
132132
href: instance-metadata-service-load-balancer.md
133133
- name: Health monitoring
134134
items:
135-
- name: Monitor load balancer
135+
- name: Monitor Load Balancer
136136
href: monitor-load-balancer.md
137-
- name: Monitoring data reference
138-
href: monitor-load-balancer-reference.md
139137
- name: Azure Monitor Insights for Load Balancer
140138
href: load-balancer-insights.md
141139
- name: Standard Load Balancer metrics and diagnostics
@@ -309,6 +307,8 @@
309307
href: /rest/api/load-balancer/loadbalancers
310308
- name: Resource Manager template
311309
href: /azure/templates/microsoft.network/loadbalancers
310+
- name: Monitoring data reference
311+
href: monitor-load-balancer-reference.md
312312
displayName: ARM
313313
- name: Resources
314314
items:

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

Lines changed: 63 additions & 68 deletions
Original file line numberDiff line numberDiff line change
@@ -1,99 +1,94 @@
11
---
2-
title: Load balancer metrics and log definitions
3-
titleSuffix: Azure Load Balancer
4-
description: Important reference material needed when you monitor Load Balancer.
5-
author: mbender-ms
2+
title: Monitoring data reference for Azure Load Balancer
3+
description: This article contains important reference material you need when you monitor Azure Load Balancer by using Azure Monitor.
4+
ms.date: 07/28/2024
5+
ms.custom: horz-monitor
66
ms.topic: reference
7+
author: mbender-ms
78
ms.author: mbender
89
ms.service: load-balancer
9-
ms.date: 05/24/2024
10-
ms.custom: subject-monitoring
1110
---
1211

13-
# Monitoring load balancer data reference
12+
# Azure Load Balancer monitoring data reference
13+
14+
[!INCLUDE [horz-monitor-ref-intro](~/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-ref-intro.md)]
15+
16+
See [Monitor Azure Load Balancer](monitor-load-balancer.md) for details on the data you can collect for Load Balancer and how to use it.
17+
18+
[!INCLUDE [horz-monitor-ref-metrics-intro](~/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-ref-metrics-intro.md)]
19+
20+
### Supported metrics for Microsoft.Network/loadBalancers
1421

15-
See [Monitoring Load Balancer](monitor-load-balancer.md) for details on collecting and analyzing monitoring data for Load Balancer.
22+
The following table lists the metrics available for the Microsoft.Network/loadBalancers resource type.
1623

17-
## Metrics
24+
[!INCLUDE [horz-monitor-ref-metrics-tableheader](~/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-ref-metrics-tableheader.md)]
1825

19-
### Load balancer metrics
26+
[!INCLUDE [Microsoft.Network/loadBalancers](~/reusable-content/ce-skilling/azure/includes/azure-monitor/reference/metrics/microsoft-network-loadbalancers-metrics-include.md)]
2027

21-
| **Metric** | **Resource type** | **Description** | **Recommended aggregation** |
22-
| ------ | ------------- | ----------- | ----------------------- |
23-
| 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 VM. 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. | Average |
28+
### Load balancer metrics
29+
30+
This table includes additional information about metrics from the Microsoft.Network/loadBalancers table:
31+
32+
| Metric | Resource type | Description | Recommended aggregation |
33+
|:------ |:------------- |:----------- |:----------------------- |
34+
| Allocated SNAT ports | Public load balancer | Standard Load Balancer reports the number of SNAT ports allocated per backend instance. | Average |
35+
| Byte count | Public and internal load balancer | Standard Load Balancer reports the data processed per front end. You might notice that the bytes aren't distributed equally across the backend instances. This behavior is expected as Azure's Load Balancer algorithm is based on flows. | Sum |
2436
| Health probe status | Public and internal load balancer | Standard Load Balancer uses a distributed health-probing service that monitors your application endpoint's health according to your configuration settings. This metric provides an aggregate or per-endpoint filtered view of each instance endpoint in the load balancer pool. You can see how Load Balancer views the health of your application, as indicated by your health probe configuration. | Average |
25-
| SYN (synchronize) count | Public and internal load balancer | Standard Load Balancer doesn’t terminate Transmission Control Protocol (TCP) connections or interact with TCP or User Data-gram Packet (UDP) flows. Flows and their handshakes are always between the source and the VM instance. To better troubleshoot your TCP protocol scenarios, you can make use of SYN packets counters to understand how many TCP connection attempts are made. The metric reports the number of TCP SYN packets that were received. | Average |
2637
| SNAT connection count | Public load balancer | Standard Load Balancer reports the number of outbound flows that are masqueraded to the Public IP address front end. Source network address translation (SNAT) ports are an exhaustible resource. This metric can give an indication of how heavily your application is relying on SNAT for outbound originated flows. Counters for successful and failed outbound SNAT flows are reported and can be used to troubleshoot and understand the health of your outbound flows. | Sum |
27-
| Allocated SNAT ports | Public load balancer | Standard Load Balancer reports the number of SNAT ports allocated per backend instance. | Average |
38+
| SYN count (synchronize) | Public and internal load balancer | Standard Load Balancer doesn’t terminate Transmission Control Protocol (TCP) connections or interact with TCP or User Data-gram Packet (UDP) flows. Flows and their handshakes are always between the source and the virtual machine instance. To better troubleshoot your TCP protocol scenarios, you can make use of SYN packets counters to understand how many TCP connection attempts are made. The metric reports the number of TCP SYN packets that were received. | Average |
2839
| Used SNAT ports | Public load balancer | Standard Load Balancer reports the number of SNAT ports that are utilized per backend instance. | Average |
29-
| Byte count | Public and internal load balancer | Standard Load Balancer reports the data processed per front end. You may notice that the bytes aren't distributed equally across the backend instances. This is expected as Azure's Load Balancer algorithm is based on flows. | Sum |
30-
| Packet count | Public and internal load balancer | Standard Load Balancer reports the packets processed per front end. | Sum |
40+
| 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. | Average |
3141

3242
### Global load balancer metrics
3343

34-
| **Metric** | **Resource type** | **Description** | **Recommended aggregation** |
35-
| ------ | ------------- | ----------- | ----------------------- |
36-
| Data path availability | Public global load balancer| Global 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 VM. 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. | Average |
37-
| Health probe status | Public global load balancer | Global load balancer uses a distributed health-probing service that monitors your application endpoint's health according to your configuration settings. This metric provides an aggregate or per-endpoint filtered view of each instance regional load balancer in the global load balancer's backend pool. You can see how global load balancer views the health of your application, as indicated by your health probe configuration. | Average |
44+
This table includes additional information about global metrics from the Microsoft.Network/loadBalancers table:
3845

39-
For more information, see a list of [all platform metrics supported in Azure Monitor for load balancer](../azure-monitor/essentials/metrics-supported.md#microsoftnetworkloadbalancers).
46+
| Metric | Resource type | Description | Recommended aggregation |
47+
|:------ |:------------- |:----------- |:----------------------- |
48+
| Health probe status | Public global load balancer | Global load balancer uses a distributed health-probing service that monitors your application endpoint's health according to your configuration settings. This metric provides an aggregate or per-endpoint filtered view of each instance regional load balancer in the global load balancer's backend pool. You can see how global load balancer views the health of your application, as indicated by your health probe configuration. | Average |
49+
| Data path availability | Public global load balancer| Global 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. | Average |
4050

41-
## Metric dimensions
51+
> [!NOTE]
52+
> Bandwidth-related metrics such as SYN packet, byte count, and packet count doesn't capture any traffic to an internal load balancer by using a UDR, such as from an NVA or firewall.
53+
>
54+
> Max and min aggregations are not available for the SYN count, packet count, SNAT connection count, and byte count metrics.
55+
> Count aggregation is not recommended for Data path availability and health probe status. Use average instead for best represented health data.
4256
43-
For more information on what metric dimensions are, see [Multi-dimensional metrics](../azure-monitor/essentials/data-platform-metrics.md#multi-dimensional-metrics).
57+
[!INCLUDE [horz-monitor-ref-metrics-dimensions-intro](~/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-ref-metrics-dimensions-intro.md)]
4458

45-
Load Balancer has the following **dimensions** associated with its metrics.
59+
[!INCLUDE [horz-monitor-ref-metrics-dimensions](~/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-ref-metrics-dimensions.md)]
4660

47-
| **Dimension Name** | **Description** |
48-
| -------------- | ----------- |
49-
| Frontend IP | The frontend IP address of one or more relevant load balancing rules |
50-
| Frontend Port | The frontend port of one or more relevant load balancing rules |
51-
| Backend IP | The backend IP address of one or more relevant load balancing rules |
52-
| Backend Port | The backend port of one or more relevant load balancing rules |
53-
| Protocol Type | The protocol of the relevant load balancing rule. The protocol can be TCP or UDP |
54-
| Direction | The direction traffic is flowing. This can be inbound or outbound. |
55-
| Connection state | The state of SNAT connection. The state can be pending, successful, or failed |
61+
| Dimension | Name | Description |
62+
|:----------|:-----|:------------|
63+
| BackendIPAddress | Backend IP | The backend IP address of one or more relevant load balancing rules |
64+
| BackendPort | Backend Port | The backend port of one or more relevant load balancing rules |
65+
| BackendRegion | | |
66+
| ConnectionState | Connection state | The state of SNAT connection. The state can be pending, successful, or failed |
67+
| Direction | Direction | The direction traffic is flowing. This value can be inbound or outbound. |
68+
| FrontendIPAddress | Frontend IP | The frontend IP address of one or more relevant load balancing rules |
69+
| FrontendPort | Frontend Port | The frontend port of one or more relevant load balancing rules |
70+
| FrontendRegion | | |
71+
| IsAwaitingRemoval | | |
72+
| ProtocolType | Protocol Type | The protocol of the relevant load balancing rule. The protocol can be TCP or UDP |
5673

57-
## Resource logs
74+
[!INCLUDE [horz-monitor-ref-resource-logs](~/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-ref-resource-logs.md)]
5875

59-
Azure Load Balancer supports Azure Activity logs and the LoadBalancerHealthEvent log category.
76+
### Supported resource logs for Microsoft.Network/loadBalancers
6077

61-
### LoadBalancerHealthEvent logs
78+
[!INCLUDE [<ResourceType/namespace>](~/reusable-content/ce-skilling/azure/includes/azure-monitor/reference/logs/microsoft-network-loadbalancers-logs-include.md)]
6279

63-
For more information on the LoadBalancerHealthEvent log category, see [Azure Load Balancer health event logs](load-balancer-health-event-logs.md).
80+
[!INCLUDE [horz-monitor-ref-logs-tables](~/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-ref-logs-tables.md)]
6481

65-
### Azure Activity logs
82+
### Load Balancer Microsoft.Network/LoadBalancers
6683

67-
The following table lists the **operations** related to Load Balancer that may be created in the Activity log.
84+
- [ALBHealthEvent](/azure/azure-monitor/reference/tables/albhealthevent#columns)
85+
- [AzureActivity](/azure/azure-monitor/reference/tables/azureactivity#columns)
6886

69-
| **Operation** | **Description** |
70-
| --- | --- |
71-
| Microsoft.Network/loadBalancers/read | Gets a load balancer definition |
72-
| Microsoft.Network/loadBalancers/write | Creates a load balancer or updates an existing load balancer |
73-
| Microsoft.Network/loadBalancers/delete | Deletes a load balancer |
74-
| Microsoft.Network/loadBalancers/backendAddressPools/queryInboundNatRulePortMapping/action | Query inbound Nat rule port mapping. |
75-
| Microsoft.Network/loadBalancers/backendAddressPools/read | Gets a load balancer backend address pool definition |
76-
| Microsoft.Network/loadBalancers/backendAddressPools/write | Creates a load balancer backend address pool or updates an existing load balancer backend address pool |
77-
| Microsoft.Network/loadBalancers/backendAddressPools/delete | Deletes a load balancer backend address pool |
78-
| Microsoft.Network/loadBalancers/backendAddressPools/join/action | Joins a load balancer backend address pool. Not Alertable. |
79-
| Microsoft.Network/loadBalancers/backendAddressPools/backendPoolAddresses/read | Lists the backend addresses of the Load Balancer backend address pool |
80-
| Microsoft.Network/loadBalancers/frontendIPConfigurations/read | Gets a load balancer frontend IP configuration definition |
81-
| Microsoft.Network/loadBalancers/frontendIPConfigurations/join/action | Joins a Load Balancer Frontend IP Configuration. Not alertable. |
82-
| Microsoft.Network/loadBalancers/inboundNatPools/read | Gets a load balancer inbound nat pool definition |
83-
| Microsoft.Network/loadBalancers/inboundNatPools/join/action | Joins a load balancer inbound NAT pool. Not alertable. |
84-
| Microsoft.Network/loadBalancers/inboundNatRules/read | Gets a load balancer inbound nat rule definition |
85-
| Microsoft.Network/loadBalancers/inboundNatRules/write | Creates a load balancer inbound nat rule or updates an existing load balancer inbound nat rule |
86-
| Microsoft.Network/loadBalancers/inboundNatRules/delete | Deletes a load balancer inbound nat rule |
87-
| Microsoft.Network/loadBalancers/inboundNatRules/join/action | Joins a load balancer inbound nat rule. Not Alertable. |
88-
| Microsoft.Network/loadBalancers/loadBalancingRules/read | Gets a load balancer load balancing rule definition |
89-
| Microsoft.Network/loadBalancers/networkInterfaces/read | Gets references to all the network interfaces under a load balancer |
90-
| Microsoft.Network/loadBalancers/outboundRules/read | Gets a load balancer outbound rule definition |
91-
| Microsoft.Network/loadBalancers/probes/read | Gets a load balancer probe |
92-
| Microsoft.Network/loadBalancers/probes/join/action | Allows using probes of a load balancer. For example, with this permission healthProbe property of virtual machine scale set can reference the probe. Not alertable. |
93-
| Microsoft.Network/loadBalancers/virtualMachines/read | Gets references to all the virtual machines under a load balancer |
87+
[!INCLUDE [horz-monitor-ref-activity-log](~/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-ref-activity-log.md)]
9488

95-
For more information on the schema of Activity Log entries, see [Activity Log schema](../azure-monitor/essentials/activity-log-schema.md).
89+
- [Microsoft.Network resource provider operations](/azure/role-based-access-control/resource-provider-operations#microsoftnetwork)
9690

97-
## See Also
91+
## Related content
9892

99-
- See [Monitoring Azure Load Balancer](./monitor-load-balancer.md) for a description of monitoring Azure Load Balancer.
93+
- See [Monitor Azure Load Balancer](monitor-load-balancer.md) for a description of monitoring Load Balancer.
94+
- See [Monitor Azure resources with Azure Monitor](/azure/azure-monitor/essentials/monitor-azure-resource) for details on monitoring Azure resources.

0 commit comments

Comments
 (0)