Skip to content

Commit cb990dd

Browse files
rmca14rmca14
authored
Merge pull request #292491 from halkazwini/avnm-vnetflow
Remove preview tag
2 parents ffdaf4d + 7680a94 commit cb990dd

File tree

1 file changed

+37
-41
lines changed

1 file changed

+37
-41
lines changed

‎articles/virtual-network-manager/concept-virtual-network-flow-logs.md

Lines changed: 37 additions & 41 deletions
Original file line numberDiff line numberDiff line change
@@ -1,82 +1,79 @@
11
---
2-
title: Monitoring security admin rules with Virtual Network Flow Logs
2+
title: Monitoring security admin rules with virtual network flow logs
33
description: This article covers using Network Watcher and Virtual Network Flow Logs to monitor traffic through security admin rules in Azure Virtual Network Manager.
44
author: mbender-ms
55
ms.author: mbender
6-
ms.topic: conceptual
6+
ms.topic: concept-article
77
ms.service: azure-virtual-network-manager
8-
ms.date: 08/11/2023
8+
ms.date: 12/31/2024
99
---
1010

11-
# Monitoring Azure Virtual Network Manager with VNet flow logs (Preview)
11+
# Monitoring Azure Virtual Network Manager with virtual network flow logs
1212

13-
Monitoring traffic is critical to understanding how your network is performing and to troubleshoot issues. Administrators can utilize VNet flow logs (Preview) to show whether traffic is flowing through or blocked on a VNet by a [security admin rule]. VNet flow logs (Preview) are a feature of Network Watcher.
13+
Monitoring traffic is critical to understanding how your network is performing and to troubleshoot issues. Administrators can utilize virtual network flow logs to show whether traffic is flowing through or blocked on a virtual network by a [security admin rule](concept-security-admins.md). Virtual network flow logs are a feature of Network Watcher.
1414

15-
Learn more about [VNet flow logs (Preview)](../network-watcher/vnet-flow-logs-overview.md) including usage and how to enable.
15+
Learn more about [virtual network flow logs](../network-watcher/vnet-flow-logs-overview.md) including usage and how to enable.
1616

17-
> [!IMPORTANT]
18-
> VNet flow logs is currently in PREVIEW. This preview version is provided without a service level agreement, and it's not recommended for production workloads. Certain features might not be supported or might have constrained capabilities. See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
17+
## Enable virtual network flow logs
1918

20-
## Enable VNet flow logs (Preview)
19+
Currently, you need to enable virtual network flow logs on each virtual network you want to monitor. You can enable virtual network flow logs on a virtual network by using the [Azure portal](../network-watcher/vnet-flow-logs-portal.md), [PowerShell](../network-watcher/vnet-flow-logs-powershell.md), or the [Azure CLI](../network-watcher/vnet-flow-logs-cli.md) guide.
2120

22-
Currently, you need to enable Virtual Network flow logs (Preview) on each VNet you want to monitor. You can enable Virtual Network Flow Logs on a VNet by using [PowerShell](../network-watcher/vnet-flow-logs-powershell.md) or the [Azure CLI](../network-watcher/vnet-flow-logs-cli.md).
23-
24-
Here's an example of a flow log
21+
Here's an example of a flow log:
2522

2623
```json
2724
{
2825
"records": [
2926
{
3027
"time": "2022-09-14T09:00:52.5625085Z",
3128
"flowLogVersion": 4,
32-
"flowLogGUID": "a1b2c3d4-e5f6-g7h8-i9j0-k1l2m3n4o5p6",
33-
"macAddress": "00224871C205",
29+
"flowLogGUID": "66aa66aa-bb77-cc88-dd99-00ee00ee00ee",
30+
"macAddress": "112233445566",
3431
"category": "FlowLogFlowEvent",
35-
"flowLogResourceID": "/SUBSCRIPTIONS/1a2b3c4d-5e6f-7g8h-9i0j-1k2l3m4n5o6p7/RESOURCEGROUPS/NETWORKWATCHERRG/PROVIDERS/MICROSOFT.NETWORK/NETWORKWATCHERS/NETWORKWATCHER_EASTUS2EUAP/FLOWLOGS/VNETFLOWLOG",
36-
"targetResourceID": "/subscriptions/1a2b3c4d-5e6f-7g8h-9i0j-1k2l3m4n5o6p7/resourceGroups/myResourceGroup/providers/Microsoft.Network/virtualNetworks/myVNet01",
32+
"flowLogResourceID": "/SUBSCRIPTIONS/aaaa0a0a-bb1b-cc2c-dd3d-eeeeee4e4e4e/RESOURCEGROUPS/NETWORKWATCHERRG/PROVIDERS/MICROSOFT.NETWORK/NETWORKWATCHERS/NETWORKWATCHER_EASTUS2EUAP/FLOWLOGS/VNETFLOWLOG",
33+
"targetResourceID": "/subscriptions/aaaa0a0a-bb1b-cc2c-dd3d-eeeeee4e4e4e/resourceGroups/myResourceGroup/providers/Microsoft.Network/virtualNetworks/myVNet",
3734
"operationName": "FlowLogFlowEvent",
3835
"flowRecords": {
3936
"flows": [
4037
{
41-
"aclID": "9a8b7c6d-5e4f-3g2h-1i0j-9k8l7m6n5o4p3",
38+
"aclID": "00aa00aa-bb11-cc22-dd33-44ee44ee44ee",
4239
"flowGroups": [
4340
{
4441
"rule": "DefaultRule_AllowInternetOutBound",
4542
"flowTuples": [
46-
"1663146003599,10.0.0.6,52.239.184.180,23956,443,6,O,B,NX,0,0,0,0",
47-
"1663146003606,10.0.0.6,52.239.184.180,23956,443,6,O,E,NX,3,767,2,1580",
48-
"1663146003637,10.0.0.6,40.74.146.17,22730,443,6,O,B,NX,0,0,0,0",
49-
"1663146003640,10.0.0.6,40.74.146.17,22730,443,6,O,E,NX,3,705,4,4569",
50-
"1663146004251,10.0.0.6,40.74.146.17,22732,443,6,O,B,NX,0,0,0,0",
51-
"1663146004251,10.0.0.6,40.74.146.17,22732,443,6,O,E,NX,3,705,4,4569",
52-
"1663146004622,10.0.0.6,40.74.146.17,22734,443,6,O,B,NX,0,0,0,0",
53-
"1663146004622,10.0.0.6,40.74.146.17,22734,443,6,O,E,NX,2,134,1,108",
54-
"1663146017343,10.0.0.6,104.16.218.84,36776,443,6,O,B,NX,0,0,0,0",
55-
"1663146022793,10.0.0.6,104.16.218.84,36776,443,6,O,E,NX,22,2217,33,32466"
43+
"1663146003599,10.0.0.6,192.0.2.180,23956,443,6,O,B,NX,0,0,0,0",
44+
"1663146003606,10.0.0.6,192.0.2.180,23956,443,6,O,E,NX,3,767,2,1580",
45+
"1663146003637,10.0.0.6,203.0.113.17,22730,443,6,O,B,NX,0,0,0,0",
46+
"1663146003640,10.0.0.6,203.0.113.17,22730,443,6,O,E,NX,3,705,4,4569",
47+
"1663146004251,10.0.0.6,203.0.113.17,22732,443,6,O,B,NX,0,0,0,0",
48+
"1663146004251,10.0.0.6,203.0.113.17,22732,443,6,O,E,NX,3,705,4,4569",
49+
"1663146004622,10.0.0.6,203.0.113.17,22734,443,6,O,B,NX,0,0,0,0",
50+
"1663146004622,10.0.0.6,203.0.113.17,22734,443,6,O,E,NX,2,134,1,108",
51+
"1663146017343,10.0.0.6,198.51.100.84,36776,443,6,O,B,NX,0,0,0,0",
52+
"1663146022793,10.0.0.6,198.51.100.84,36776,443,6,O,E,NX,22,2217,33,32466"
5653
]
5754
}
5855
]
5956
},
6057
{
61-
"aclID": "b1c2d3e4-f5g6-h7i8-j9k0-l1m2n3o4p5q6",
58+
"aclID": "00aa00aa-bb11-cc22-dd33-44ee44ee44ee",
6259
"flowGroups": [
6360
{
6461
"rule": "BlockHighRiskTCPPortsFromInternet",
6562
"flowTuples": [
66-
"1663145998065,101.33.218.153,10.0.0.6,55188,22,6,I,D,NX,0,0,0,0",
67-
"1663146005503,192.241.200.164,10.0.0.6,35276,119,6,I,D,NX,0,0,0,0"
63+
"1663145998065,203.0.113.153,10.0.0.6,55188,22,6,I,D,NX,0,0,0,0",
64+
"1663146005503,192.0.2.164,10.0.0.6,35276,119,6,I,D,NX,0,0,0,0"
6865
]
6966
},
7067
{
7168
"rule": "Internet",
7269
"flowTuples": [
73-
"1663145989563,20.106.221.10,10.0.0.6,50557,44357,6,I,D,NX,0,0,0,0",
74-
"1663145989679,20.55.117.81,10.0.0.6,62797,35945,6,I,D,NX,0,0,0,0",
75-
"1663145989709,20.55.113.5,10.0.0.6,51961,65515,6,I,D,NX,0,0,0,0",
76-
"1663145990049,13.65.224.51,10.0.0.6,40497,40129,6,I,D,NX,0,0,0,0",
77-
"1663145990145,20.55.117.81,10.0.0.6,62797,30472,6,I,D,NX,0,0,0,0",
78-
"1663145990175,20.55.113.5,10.0.0.6,51961,28184,6,I,D,NX,0,0,0,0",
79-
"1663146015545,20.106.221.10,10.0.0.6,50557,31244,6,I,D,NX,0,0,0,0"
70+
"1663145989563,192.0.2.10,10.0.0.6,50557,44357,6,I,D,NX,0,0,0,0",
71+
"1663145989679,203.0.113.81,10.0.0.6,62797,35945,6,I,D,NX,0,0,0,0",
72+
"1663145989709,203.0.113.5,10.0.0.6,51961,65515,6,I,D,NX,0,0,0,0",
73+
"1663145990049,198.51.100.51,10.0.0.6,40497,40129,6,I,D,NX,0,0,0,0",
74+
"1663145990145,203.0.113.81,10.0.0.6,62797,30472,6,I,D,NX,0,0,0,0",
75+
"1663145990175,203.0.113.5,10.0.0.6,51961,28184,6,I,D,NX,0,0,0,0",
76+
"1663146015545,192.0.2.10,10.0.0.6,50557,31244,6,I,D,NX,0,0,0,0"
8077
]
8178
}
8279
]
@@ -89,8 +86,7 @@ Here's an example of a flow log
8986

9087
```
9188

89+
## Related content
9290

93-
## Next steps
94-
> [!div class="nextstepaction"]
95-
> Learn more about [VNet Flow Logs](../network-watcher/vnet-flow-logs-overview.md) and how to use them.
96-
> Learn more about [Event log options for Azure Virtual Network Manager](concept-event-logs.md).
91+
- Learn more about [virtual network flow logs](../network-watcher/vnet-flow-logs-overview.md) and how to use them.
92+
- Learn more about [Event log options for Azure Virtual Network Manager](concept-event-logs.md).

0 commit comments

Comments
 (0)