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/security-center/continuous-export.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,9 +18,9 @@ This article describes the set of (preview) tools that allow you to export alert
18
18
19
19
Using these tools you can:
20
20
21
-
*Continously export to Log Analytics workspaces
22
-
*Continously export to Azure Event Hubs (for integrations with third-party SIEMs)
23
-
*Perform a one-time export to CSV
21
+
*Continuously export to Log Analytics workspaces
22
+
*Continuously export to Azure Event Hubs (for integrations with third-party SIEMs)
23
+
*Export to CSV (one time)
24
24
25
25
26
26
## Setting up a continuous export
@@ -46,7 +46,7 @@ The steps below are necessary whether you're setting up a continuous export to L
46
46
47
47
## Configuring SIEM integration via Azure Event Hubs
48
48
49
-
Azure Event Hubs is a great solution for programatically consuming any streaming data. In the case of Azure Security Center alerts and recommendations, it's the preferred way to integrate with a third-party SIEM.
49
+
Azure Event Hubs is a great solution for programatically consuming any streaming data. For Azure Security Center alerts and recommendations, it's the preferred way to integrate with a third-party SIEM.
50
50
51
51
> [!NOTE]
52
52
> The most effective method to stream monitoring data to external tools in most cases is using Azure Event Hubs. [This article](https://docs.microsoft.com/azure/azure-monitor/platform/stream-monitoring-data-event-hubs) provides a brief description for how you can stream monitoring data from different sources to an Event Hub and links to detailed guidance.
0 commit comments