Skip to content

Commit c7b5135

Browse files
committedJan 23, 2020
updates
1 parent f91d0cc commit c7b5135

File tree

9 files changed

+50
-42
lines changed

9 files changed

+50
-42
lines changed
 

‎articles/stream-analytics/debug-locally-using-job-diagram.md

Lines changed: 50 additions & 42 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.author: sujie
66
ms.reviewer: mamccrea
77
ms.service: stream-analytics
88
ms.topic: conceptual
9-
ms.date: 01/21/2020
9+
ms.date: 01/23/2020
1010
---
1111

1212
# Debug Azure Stream Analytics queries locally using job diagram in Visual Studio
@@ -15,7 +15,7 @@ Jobs that output no result or unexpected results are common troubleshooting scen
1515

1616
## Debug a query using job diagram
1717

18-
An Azure Stream Analytics script is used to transform input data to output data. The job diagram shows how data flows from input sources (Event Hub, IoT Hub, etc) through multiple query steps and finally output to sinks. Each query step is mapped to a temporary result set defined in the script using a `WITH` statement. You can view the data as well as metrics of each query step in each intermediate result set to find the source of an issue.
18+
An Azure Stream Analytics script is used to transform input data to output data. The job diagram shows how data flows from input sources (Event Hub, IoT Hub, etc) through multiple query steps and, finally, to output sinks. Each query step is mapped to a temporary result set defined in the script using a `WITH` statement. You can view the data as well as metrics of each query step in each intermediate result set to find the source of an issue.
1919

2020
> [!NOTE]
2121
> This job diagram only shows the data and metrics for local testing in a single node. It should not be used for performance tuning and troubleshooting.
@@ -31,66 +31,74 @@ Choose the input and output source from the script editor and select **Run local
3131

3232
### View the intermediate result set
3333

34-
#### Navigate to script
35-
3634
1. Select the query step to navigate to the script. You are automatically directed to the corresponding script in the editor on the left.
3735

38-
![Job diagram navigate script](./media/vs-job-diagram/navigate-script.png)
39-
40-
#### Preview result set
36+
![Job diagram navigate script](./media/debug-locally-using-job-diagram/navigate-script.png)
4137

42-
Select the query step and select **Preview** in the popped up dialog. The result set is shown in a tab in the bottom result window.
38+
2. Select the query step and select **Preview** in the popped up dialog. The result set is shown in a tab in the bottom result window.
4339

44-
![Job diagram preview result](./media/vs-job-diagram/preview-result.png)
40+
![Job diagram preview result](./media/debug-locally-using-job-diagram/preview-result.png)
4541

4642
### View step metrics
4743

48-
* **Input sources (Live stream)**
44+
In this section, you explore the metrics available for each part of the diagram.
45+
46+
#### Input sources (Live stream)
4947

50-
![Job diagram live input sources](./media/vs-job-diagram/live-input.png)
48+
![Job diagram live input sources](./media/debug-locally-using-job-diagram/live-input.png)
5149

52-
* **TaxiRide**: The name of the input.
53-
* **Event Hub**: Input source type.
54-
* **Events**: The number of events read.
55-
* **Backlogged Event Sources**: How many more messages need to be read for Event Hubs and IoT Hub inputs.
56-
* **Events in Bytes**:The number of bytes read.
57-
* **Degraded Events**:The count of events that had an issue other than with deserialization.
58-
* **Early Events**: The number of events that have an application timestamp before the high watermark.
59-
* **Late Events**: The number of events that have an application timestamp after the high watermark.
60-
* **Event Sources**: The number of data units read. For example, the number of blobs.
50+
|Metric|Description|
51+
|-|-|
52+
|**TaxiRide**| The name of the input.|
53+
|**Event Hub** | Input source type.|
54+
|**Events**|The number of events read.|
55+
|**Backlogged Event Sources**|How many more messages need to be read for Event Hubs and IoT Hub inputs.|
56+
|**Events in Bytes**|The number of bytes read.|
57+
| **Degraded Events**|The count of events that had an issue other than with deserialization.|
58+
|**Early Events**| The number of events that have an application timestamp before the high watermark.|
59+
|**Late Events**| The number of events that have an application timestamp after the high watermark.|
60+
|**Event Sources**| The number of data units read. For example, the number of blobs.|
6161

62-
* **Input sources (Local input)**
62+
#### Input sources (Local input)
6363

64-
![Job diagram local input sources](./media/vs-job-diagram/local-input.png)
64+
![Job diagram local input sources](./media/debug-locally-using-job-diagram/local-input.png)
6565

66-
* **TaxiRide**: The name of the input.
67-
* **Row Count**: The number of rows generated from the step.
68-
* **Data Size**: The size of data generated from this step.
69-
* **Local input**: Use local data as input.
66+
|Metric|Description|
67+
|-|-|
68+
|**TaxiRide**| The name of the input.|
69+
|**Row Count**| The number of rows generated from the step.|
70+
|**Data Size**| The size of data generated from this step.|
71+
|**Local input**| Use local data as input.|
7072

71-
* **Query steps**
73+
#### Query steps
7274

73-
![Job diagram query step](./media/vs-job-diagram/query-step.png)
75+
![Job diagram query step](./media/debug-locally-using-job-diagram/query-step.png)
7476

75-
* **TripData**: The name of the temporary result set.
76-
* **Row Count**: The number of rows generated from the step.
77-
* **Data Size**: The size of data generated from this step.
77+
|Metric|Description|
78+
|-|-|
79+
|**TripData**|The name of the temporary result set.|
80+
|**Row Count**| The number of rows generated from the step.|
81+
|**Data Size**| The size of data generated from this step.|
7882

79-
* **Output sinks** (Live output)
83+
#### Output sinks (Live output)
8084

81-
![Job diagram local output sinks](./media/vs-job-diagram/live-output.png)
85+
![Job diagram local output sinks](./media/debug-locally-using-job-diagram/live-output.png)
8286

83-
* **regionaggEH**: The name of the output.
84-
* **Events**: The number of events output to sinks.
87+
|Metric|Description|
88+
|-|-|
89+
|**regionaggEH**|The name of the output.|
90+
|**Events**|The number of events output to sinks.|
8591

86-
* **Output sinks** (Local output)
92+
#### Output sinks (Local output)
8793

88-
![Job diagram local output sinks](./media/vs-job-diagram/local-output.png)
94+
![Job diagram local output sinks](./media/debug-locally-using-job-diagram/local-output.png)
8995

90-
* **regionaggEH**: The name of the output.
91-
* **Local Output**: Result output to a local file.
92-
* **Row Count**: The number of rows output to the local file.
93-
* **Data Size**: The size of data output to the local file.
96+
|Metric|Description|
97+
|-|-|
98+
|**regionaggEH**|The name of the output.|
99+
|**Local Output**| Result output to a local file.|
100+
|**Row Count**| The number of rows output to the local file.|
101+
|**Data Size**| The size of data output to the local file.|
94102

95103
### Close job diagram
96104

@@ -100,7 +108,7 @@ If you don't need the job diagram anymore, select **Close** on the top right cor
100108

101109
Other job level metrics shows up in the pop up console. Press **Ctrl+C** in the console if you want to stop the job.
102110

103-
![Job diagram stop job](./media/vs-job-diagram/stop-job.png)
111+
![Job diagram stop job](./media/debug-locally-using-job-diagram/stop-job.png)
104112

105113
## Limitations
106114

Loading
Loading
Loading
Loading
Loading
Loading
Loading
Loading

0 commit comments

Comments
 (0)
Please sign in to comment.