Skip to content

Commit 9284905

Browse files
authored
Added Events Hubs Support
ERTC now supports Event Hubs as an export destination. Added this information and a link to EH info.
1 parent 259f022 commit 9284905

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/expressroute/traffic-collector.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ ms.custom: references_regions
1313

1414
# Azure ExpressRoute Traffic Collector
1515

16-
ExpressRoute Traffic Collector enables sampling of network flows sent over your ExpressRoute circuits. Flow logs get sent to a [Log Analytics workspace](/azure/azure-monitor/logs/log-analytics-overview) where you can create your own log queries for further analysis. You can also export the data to any visualization tool or SIEM (Security Information and Event Management) of your choice. Flow logs can be enabled for both private peering and Microsoft peering with ExpressRoute Traffic Collector.
16+
ExpressRoute Traffic Collector enables sampling of network flows sent over your ExpressRoute circuits. Flow logs are sent to an export destination where you can create your own log queries for further analysis. Supported destinations include [Log Analytics](/azure/azure-monitor/logs/log-analytics-overview), [Event Hubs](/azure/event-hubs/event-hubs-about), and Storage Accounts. You can also export the data to any visualization tool or SIEM (Security Information and Event Management) of your choice. Flow logs can be enabled for both private peering and Microsoft peering with ExpressRoute Traffic Collector.
1717

1818
:::image type="content" source="./media/traffic-collector/main-diagram.png" alt-text="Diagram of ExpressRoute traffic collector in an Azure environment.":::
1919

0 commit comments

Comments
 (0)