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: docs/integrations/microsoft-azure/azure-stream-analytics.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,8 +14,8 @@ import useBaseUrl from '@docusaurus/useBaseUrl';
14
14
15
15
For Azure Stream Analytics, you can collect the following logs and metrics:
16
16
17
-
***Resource logs**. Azure Stream Analytics captures below two categories of resource logs:
18
-
***Authoring**. These log events that are related to job authoring operations, such as job creation, and starting or stopping the job.
17
+
***Resource logs**. Azure Stream Analytics captures the following two categories of resource logs:
18
+
***Authoring**. These log events are related to job authoring operations, such as job creation, and starting or stopping the job.
19
19
***Execution**. These events are related to job execution such as connectivity and data processing errors.
20
20
21
21
To learn more about the different resource log category types and schemas collected for Azure Stream Analytics, refer to the [Azure documentation](https://learn.microsoft.com/en-us/azure/stream-analytics/stream-analytics-job-diagnostic-logs#resource-log-categories).
@@ -35,25 +35,25 @@ When you configure the event hubs source or HTTP source, plan your source catego
35
35
36
36
### Configure metrics collection
37
37
38
-
In this section, you will configure a pipeline for shipping metrics from Azure Monitor to an Event Hub, on to an Azure Function, and finally to an HTTP Source on a hosted collector in Sumo Logic.
38
+
In this section, you will configure a pipeline for shipping metrics from Azure Monitor to an Event Hub, onto an Azure Function, and finally to an HTTP Source on a hosted collector in Sumo Logic.
39
39
40
40
1. Create a hosted collector and tag the `tenant_name` field. You can get the tenant name using the instructions [here](https://learn.microsoft.com/en-us/azure/active-directory-b2c/tenant-management-read-tenant-name#get-your-tenant-name). <br/><img src={useBaseUrl('img/integrations/microsoft-azure/Azure-Storage-Tag-Tenant-Name.png')} alt="Azure Tag Tenant Name" style={{border: '1px solid gray'}} width="500" />
41
41
1.[Configure an HTTP Source](/docs/send-data/collect-from-other-data-sources/azure-monitoring/collect-metrics-azure-monitor/#step-1-configure-an-http-source).
42
42
1.[Configure and deploy the ARM Template](/docs/send-data/collect-from-other-data-sources/azure-monitoring/collect-metrics-azure-monitor/#step-2-configure-azure-resources-using-arm-template).
43
-
1.[Export metrics to Event Hub](/docs/send-data/collect-from-other-data-sources/azure-monitoring/collect-metrics-azure-monitor/#step-3-export-metrics-for-a-particular-resource-to-event-hub). Perform below steps for each Azure Stream Analytics job that you want to monitor.
44
-
* Choose `Stream to an event hub` as destination.
43
+
1.[Export metrics to Event Hub](/docs/send-data/collect-from-other-data-sources/azure-monitoring/collect-metrics-azure-monitor/#step-3-export-metrics-for-a-particular-resource-to-event-hub). Perform the steps below for each Azure Stream Analytics job that you want to monitor.
44
+
* Choose `Stream to an event hub` as the destination.
45
45
* Select `AllMetrics`.
46
-
* Use the Event hub namespace created by the ARM template in Step 2 above. You can create a new Event hub or use the one created by ARM template. You can use the default policy `RootManageSharedAccessKey` as the policy name.
46
+
* Use the Event hub namespace created by the ARM template in Step 2 above. You can create a new Event hub or use the one created by the ARM template. You can use the default policy `RootManageSharedAccessKey` as the policy name.
47
47
48
48
### Configure logs collection
49
49
50
50
In this section, you will configure a pipeline for shipping diagnostic logs from Azure Monitor to an Event Hub.
51
51
52
52
1. To set up the Azure Event Hubs source in Sumo Logic, refer to [Azure Event Hubs Source for Logs](/docs/send-data/collect-from-other-data-sources/azure-monitoring/ms-azure-event-hubs-source/).
53
-
2. To create the Diagnostic settings in Azure portal, refer to the [Azure documentation](https://learn.microsoft.com/en-us/azure/stream-analytics/stream-analytics-job-diagnostic-logs#send-diagnostics-to-azure-monitor-logs). Perform below steps for each Azure Stream Analytics job that you want to monitor.
53
+
2. To create the Diagnostic settings in the Azure portal, refer to the [Azure documentation](https://learn.microsoft.com/en-us/azure/stream-analytics/stream-analytics-job-diagnostic-logs#send-diagnostics-to-azure-monitor-logs). Perform the steps below for each Azure Stream Analytics job that you want to monitor.
54
54
* Choose `Stream to an event hub` as the destination.
55
55
* Select `Execution` and `Authoring`.
56
-
* Use the Event hub namespace and Event hub name configured in previous step in destination details section. You can use the default policy `RootManageSharedAccessKey` as the policy name.
56
+
* Use the Event hub namespace and Event hub name configured in the previous step in the destination details section. You can use the default policy `RootManageSharedAccessKey` as the policy name.
0 commit comments