Skip to content

Commit 49888a8

Browse files
Merge pull request #285555 from cozhang8/patch-5
Update monitor-load-balancer.md
2 parents 283f69d + 2594698 commit 49888a8

File tree

1 file changed

+21
-5
lines changed

1 file changed

+21
-5
lines changed

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

Lines changed: 21 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -238,14 +238,30 @@ az monitor diagnostic-settings create \
238238

239239
[!INCLUDE [horz-monitor-external-tools](~/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-external-tools.md)]
240240

241-
## Analyzing Load Balancer Traffic with NSG flow logs
241+
## Analyzing Load Balancer Traffic with VNet flow logs
242242

243-
[NSG flow logs](../network-watcher/nsg-flow-logs-overview.md) is a feature of Azure Network Watcher that allows you to log information about IP traffic flowing through a network security group. Flow data is sent to Azure Storage from where you can access it and export it to a visualization tool, security information and event management (SIEM) solution, or intrusion detection system (IDS).
243+
[Virtual network flow logs](../network-watcher/vnet-flow-logs-overview.md) are a feature of Azure Network Watcher that logs information about IP traffic flowing through a virtual network. Flow data from virtual network flow logs is sent to Azure Storage. From there, you can access the data and export it to any visualization tool, security information and event management (SIEM) solution, or intrusion detection system (IDS).
244+
245+
For general guidance on creating and managing virtual network flow logs, see [Manage virtual network flow logs](../network-watcher/vnet-flow-logs-portal.md). Once you have created your virtual network flow logs, you can access the data on [Log Analytics workspaces](/azure/azure-monitor/logs/log-analytics-overview) where you can also query and filter the data to identify traffic flowing through your Load Balancer. See [Traffic analytics schema and data aggregation](../network-watcher/traffic-analytics-schema.md) for more details on the virtual network flow logs schema.
246+
247+
You can also enable [Traffic Analytics](../network-watcher/traffic-analytics.md) when you are creating your virtual network flow logs which provides insights and visualizations on the flow log data such as traffic distribution, traffic pattern, application ports utilized, and top talkers in your virtual network.
248+
## Log Analytics query for VNet flow logs
249+
To view logs for inbound flows connected to a specific Load Balancer:
250+
251+
```Kusto
252+
NTANetAnalytics
253+
| where DestLoadBalancer == '<Subscription ID>/<Resource Group name>/<Load Balancer name>'
254+
```
255+
256+
1. Use the query above in your Log Analytics workspace and update the string with the valid values for your Load Balancer. To learn more about using Log Analytics, see [Log Analytics tutorial](/azure/azure-monitor/logs/log-analytics-tutorial).
257+
258+
1. To view the source IP of the connection, either the `SrcIp` or `SrcPublicIps` column will be populated. All traffic originating from public non-malicious or Azure service-owned IP addresses will appear in `SrcPublicIps` and all other source IPs will appear in `SrcIP`. If you want more details on the type of traffic, you can use the `FlowType` column to filter for different types of IP addresses involved in the flow. See [Traffic analytics schema and data aggregation notes](../network-watcher/traffic-analytics-schema.md#notes) for `FlowType` field definitions.
259+
260+
1. Identify the backend pool instances being used in the inbound connection through any of the following columns: `DestIP`, `MacAddress`, `DestVM`, `TargetResourceID`, `DestNic`.
261+
262+
1. Through these logs, you can gather further information about the connections going through your Load Balancer such as port information, protocol, and traffic size through packet and byte count sent from destination and source.
244263

245-
NSG flow logs can be used to analyze traffic flowing through the load balancer.
246264

247-
> [!NOTE]
248-
> NSG flow logs don't contain the load balancers frontend IP address. To analyze the traffic flowing into a load balancer, the NSG flow logs would need to be filtered by the private IP addresses of the load balancer’s backend pool members.
249265

250266
[!INCLUDE [horz-monitor-kusto-queries](~/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-kusto-queries.md)]
251267

0 commit comments

Comments
 (0)