You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/network-watcher/vnet-flow-logs-overview.md
+18-2Lines changed: 18 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ author: halkazwini
6
6
ms.author: halkazwini
7
7
ms.service: azure-network-watcher
8
8
ms.topic: concept-article
9
-
ms.date: 07/11/2024
9
+
ms.date: 08/10/2024
10
10
11
11
#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.
Virtual network flow logs have the following properties:
77
77
78
78
-`time`: Time in UTC when the event was logged.
79
-
-`flowLogVersion`: Version of the flow log schema.
79
+
-`flowLogVersion`: Version of the flow log.
80
80
-`flowLogGUID`: Resource GUID of the `FlowLog` resource.
81
81
-`macAddress`: MAC address of the network interface where the event was captured.
82
82
-`category`: Category of the event. The category is always `FlowLogFlowEvent`.
@@ -219,6 +219,22 @@ For continuation (`C`) and end (`E`) flow states, byte and packet counts are agg
219
219
220
220
- Storage of logs is charged separately. For more information, see [Azure Blob Storage pricing](https://azure.microsoft.com/pricing/details/storage/blobs/).
221
221
222
+
## Supported scenarios
223
+
224
+
The following table outlines the support scope of flow logs.
0 commit comments