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/stream-analytics/stream-analytics-job-diagnostic-logs.md
+6-6Lines changed: 6 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -7,12 +7,12 @@ ms.author: jeanb
7
7
ms.reviewer: jasonh
8
8
ms.service: stream-analytics
9
9
ms.topic: conceptual
10
-
ms.date: 12/07/2018
10
+
ms.date: 01/10/2018
11
11
ms.custom: seodec18
12
12
---
13
13
# Troubleshoot Azure Stream Analytics by using diagnostics logs
14
14
15
-
Occasionally, an Azure Stream Analytics job unexpectedly stops processing. It's important to be able to troubleshoot this kind of event. The event might be caused by an unexpected query result, by connectivity to devices, or by an unexpected service outage. The diagnostics logs in Stream Analytics can help you identify the cause of issues when they occur, and reduce recovery time.
15
+
Occasionally, an Azure Stream Analytics job unexpectedly stops processing. It's important to be able to troubleshoot this kind of event. The event might be caused by an unexpected query result, by connectivity to devices, or by an unexpected service outage. The diagnostics logs in Stream Analytics can help you identify the cause of issues when they occur and reduce recovery time.
16
16
17
17
## Log types
18
18
@@ -24,17 +24,17 @@ Stream Analytics offers two types of logs:
24
24
> You can use services like Azure Storage, Azure Event Hubs, and Azure Log Analytics to analyze nonconforming data. You are charged based on the pricing model for those services.
25
25
>
26
26
27
-
## Turn on diagnostics logs
27
+
## Send diagnostics to Log Analytics
28
28
29
29
Diagnostics logs are **off** by default. To turn on diagnostics logs, complete these steps:
30
30
31
-
1. Sign in to the Azure portal, and go to the streaming job blade. Under **Monitoring**, select **Diagnostics logs**.
31
+
1. Sign in to the Azure portal, and navigate to your Stream Analytics job. Under **Monitoring**, select **Diagnostics logs**. Then select **Turn on diagnostics**.
32
32
33
33

34
34
35
-
2.Select **Turn on diagnostics**.
35
+
2.Create a **Name** in **Diagnostic settings** and check the box next to **Send to Log Analytics**. Then add an existing or create a new **Log analytics workspace**. Check the boxes for **Execution** and **Authoring** under **LOG**.
36
36
37
-

37
+

38
38
39
39
3. On the **Diagnostics settings** page, for **Status**, select **On**.
Copy file name to clipboardExpand all lines: articles/stream-analytics/stream-analytics-set-up-alerts.md
+35-12Lines changed: 35 additions & 12 deletions
Original file line number
Diff line number
Diff line change
@@ -7,37 +7,60 @@ ms.author: jeanb
7
7
ms.reviewer: mamccrea
8
8
ms.service: stream-analytics
9
9
ms.topic: conceptual
10
-
ms.date: 12/07/2018
10
+
ms.date: 01/10/2019
11
11
ms.custom: seodec18
12
12
---
13
13
# Set up alerts for Azure Stream Analytics jobs
14
-
You can set up alerts to trigger an alert when a metric reaches a condition that you specify. For example, you might set up an alert for a condition like the following:
15
14
16
-
`If there are zero input events in the last 5 minutes, send email notification to sa-admin@example.com`
15
+
It is important to monitor your Azure Stream Analytics job to ensure the job is running continuously without any problems. This article describes how to set up alerts for common scenarios that should be monitored.
17
16
18
17
Rules can be set up on metrics through the portal, or can be configured [programmatically](https://code.msdn.microsoft.com/windowsazure/Receive-Email-Notifications-199e2c9a) over Operation Logs data.
19
18
20
19
## Set up alerts in the Azure portal
21
-
1. In the Azure portal, open the Stream Analytics job you want to create an alert for.
22
20
23
-
2. In the **Job** blade, click the **Monitoring** section.
21
+
1. In the Azure portal, open the Stream Analytics job you want to create an alert for.
24
22
25
-
3. In the **Metric**blade, click the **Add alert**command.
23
+
2. On the **Job**page, navigate to the the **Monitoring**section.
5. Use the selectors to define the condition under which the alert will be sent.
29
+
4. Your Stream Analytics job name should automatically appear under **RESOURCE**. Click **Add condition**, and select **All Administrative operations** under **Configure signal logic**.
32
30
33
-
6. Provide information about where the alert should go.
31
+

34
32
35
-

33
+
5. Under **Configure signal logic**, change **Event Level** to **All** and change **Status** to **Failed**. Leave **Event initiated by** blank and click **Done**.
36
34
37
-
For more detail on configuring alerts in the Azure portal, see [Receive alert notifications](../monitoring-and-diagnostics/insights-receive-alert-notifications.md).
35
+

36
+
37
+
6. Select an existing action group or create a new group. In this example, a new action group called **TIDashboardGroupActions** was created with an **Emails** action that sends an email to users with the **Owner** Azure Resource Manager Role.
38
+
39
+

40
+
41
+
7. The **RESOURCE**, **CONDITION**, and **ACTION GROUPS** should each have an entry.
Add an **Alert rule name**, **Description**, and your **Resource Group** to the **ALERT DETAILS** and click **Create alert rule** to create the rule for your Stream Analytics job.
The following alerts are recommended for monitoring the performance of your Stream Analytics job. These metrics should be evaluated every minute over the last 5-minute period. If your job suffers from performance issues, you can leverage query parallelization to make it more optimal and try increasing the number of streaming units.
|SU% Utilization|Greater than|Maximum|80|There are multiple factors that increase SU% Utilization. You can scale with query parallelization or increase the number of streaming units.|
56
+
|Runtime errors|Greater than|Total|0|Examine the activity or diagnostic logs and make appropriate changes to the inputs, query or outputs.|
57
+
|Watermark delay|Greater than|Maximum|When average value of this metric over the last 15 minutes is greater than late arrival tolerance (in seconds). If you have not modified the late arrival tolerance, the default is set to 5 seconds.|Try increasing the number of SUs or parallelizing your query.|
58
+
|Input deserialization errors|Greater than|Total|0|Examine the activity or diagnostic logs and make appropriate changes to the input.|
39
59
40
60
## Get help
61
+
62
+
For more detail on configuring alerts in the Azure portal, see [Receive alert notifications](../monitoring-and-diagnostics/insights-receive-alert-notifications.md).
63
+
41
64
For further assistance, try our [Azure Stream Analytics forum](https://social.msdn.microsoft.com/Forums/azure/home?forum=AzureStreamAnalytics)
0 commit comments