Skip to content

Commit cfcb5e6

Browse files
Merge pull request #289818 from halkazwini/nw-vnetflow
Updates: Virtual network flow logs
2 parents c0a0926 + ef9c375 commit cfcb5e6

File tree

1 file changed

+8
-2
lines changed

1 file changed

+8
-2
lines changed

articles/network-watcher/vnet-flow-logs-overview.md

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: halkazwini
66
ms.author: halkazwini
77
ms.service: azure-network-watcher
88
ms.topic: concept-article
9-
ms.date: 10/25/2024
9+
ms.date: 11/04/2024
1010

1111
#CustomerIntent: As an Azure administrator, I want to learn about virtual network flow logs so that I can log my network traffic to analyze and optimize network performance.
1212
---
@@ -206,13 +206,19 @@ Here's an example bandwidth calculation for flow tuples from a TCP conversation
206206

207207
For continuation (`C`) and end (`E`) flow states, byte and packet counts are aggregate counts from the time of the previous flow's tuple record. In the example conversation, the total number of packets transferred is 1,021 + 52 + 8,005 + 47 = 9,125. The total number of bytes transferred is 588,096 + 29,952 + 4,610,880 + 27,072 = 5,256,000.
208208

209-
## Storage account considerations for virtual network flow logs
209+
## Considerations for virtual network flow logs
210+
211+
### Storage account
210212

211213
- **Location**: The storage account must be in the same region as the virtual network.
212214
- **Subscription**: The storage account must be in the same subscription of the virtual network or in a subscription associated with the same Microsoft Entra tenant of the virtual network's subscription.
213215
- **Performance tier**: The storage account must be standard. Premium storage accounts aren't supported.
214216
- **Self-managed key rotation**: If you change or rotate the access keys to your storage account, virtual network flow logs stop working. To fix this problem, you must disable and then re-enable virtual network flow logs.
215217

218+
### Private endpoint traffic
219+
220+
Traffic can't be recorded at the private endpoint itself. You can capture traffic to a private endpoint at the source VM. The traffic is recorded with source IP address of the VM and destination IP address of the private endpoint. You can use `PrivateEndpointResourceId` field to identify traffic flowing to a private endpoint. For more information, see [Traffic analytics schema](traffic-analytics-schema.md?tabs=vnet#traffic-analytics-schema).
221+
216222
## Pricing
217223

218224
- Virtual network flow logs are charged per gigabyte of ***Network flow logs collected*** and come with a free tier of 5 GB/month per subscription.

0 commit comments

Comments
 (0)