Skip to content

Commit 0ada47a

Browse files
authored
Update traffic-collector.md
1 parent 863024e commit 0ada47a

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

articles/expressroute/traffic-collector.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -43,6 +43,8 @@ Flow logs can help you look into various traffic insights. Some common use cases
4343

4444
Flow logs are collected at an interval of every 1 minute. All packets collected for a given flow get aggregated and imported into a Log Analytics workspace for further analysis. During flow collection, not every packet is captured into its own flow record. ExpressRoute Traffic Collector uses a sampling rate of 1:4096, meaning 1 out of every 4096 packets gets captured. Therefore, sampling rate short flows (in total bytes) might not get collected. This sampling size doesn't affect network traffic analysis when sampled data is aggregated over a longer period of time. Flow collection time and sampling rate are fixed and can't be changed.
4545

46+
>See [ExpressRoute limits](../azure-resource-manager/management/azure-subscription-service-limits.md#expressroute-limits) for Maximum number of flows
47+
4648
## Supported ExpressRoute Circuits
4749

4850
ExpressRoute Traffic Collector supports both Provider-managed circuits and ExpressRoute Direct circuits. At this time, ExpressRoute Traffic Collector only supports circuits with a bandwidth of 1Gbps or greater.

0 commit comments

Comments
 (0)