Skip to content

Commit a493671

Browse files
authored
update the sentence
Thinking an advice.
1 parent 3f224ab commit a493671

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/network-watcher/network-watcher-nsg-flow-logging-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -398,7 +398,7 @@ $virtualNetwork | Set-AzVirtualNetwork
398398

399399
Few common scenarios:
400400
1. **Multiple NICs at a VM**: In case multiple NICs are attached to a virtual machine, flow logging must be enabled on all of them
401-
1. **Having NSG at both NIC and Subnet Level**: In case NSG is configured at the NIC as well as the subnet level, then flow logging must be enabled at both the NSGs since the exact sequence of rule processing by NSGs at NIC and subnet level is platform dependent and varies from case to case. There is no guarantee which NSG flow logs will be logged. You have to check both of the flow logs.
401+
1. **Having NSG at both NIC and Subnet Level**: In case NSG is configured at the NIC as well as the subnet level, then flow logging must be enabled at both the NSGs since the exact sequence of rule processing by NSGs at NIC and subnet level is platform dependent and varies from case to case. Traffic flows will be logged against the NSG which is processed last. The processing order is changed by the platform state. You have to check both of the flow logs.
402402
1. **AKS Cluster Subnet**: AKS adds a default NSG at the cluster subnet. As explained in the above point, flow logging must be enabled on this default NSG.
403403

404404
**Storage provisioning**: Storage should be provisioned in tune with expected Flow Log volume.

0 commit comments

Comments
 (0)