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-real-time-fraud-detection.md
+23-24Lines changed: 23 additions & 24 deletions
Original file line number
Diff line number
Diff line change
@@ -37,16 +37,17 @@ Before you start, make sure you have completed the following steps:
37
37
38
38
Sign in to the [Azure portal](https://portal.azure.com).
39
39
40
-
## Create an Azure Event Hub
40
+
## Create an event hub
41
41
42
42
Before Stream Analytics can analyze the fraudulent calls data stream, the data needs to be sent to Azure. In this tutorial, you will send data to Azure by using [Azure Event Hubs](../event-hubs/event-hubs-about.md).
43
43
44
-
Use the following steps to create an Event Hub and send call data to that Event Hub:
44
+
Use the following steps to create an event hub and send call data to that event hub:
45
45
46
46
1. Sign in to the [Azure portal](https://portal.azure.com/).
47
47
2. Select **Create a resource** > **Internet of Things** > **Event Hubs**.
48
48
49
-

49
+

50
+
50
51
3. Fill out the **Create Namespace** pane with the following values:
51
52
52
53
|**Setting**|**Suggested value**|**Description**|
@@ -58,13 +59,13 @@ Use the following steps to create an Event Hub and send call data to that Event
58
59
59
60
4. Use default options on the remaining settings and select **Review + create**. Then select **Create** to start the deployment.
60
61
61
-

62
+

62
63
63
64
5. When the namespace has finished deploying, go to **All resources** and find *asaTutorialEventHub* in the list of Azure resources. Select *asaTutorialEventHub* to open it.
64
65
65
-
6. Next select **+Event Hub** and enter a **Name** for the Event Hub. Set the **Partition Count** to 2. Use the default options in the remaining settings and select **Create**. Then wait for the deployment to succeed.
66
+
6. Next select **+Event Hub** and enter a **Name** for the event hub. Set the **Partition Count** to 2. Use the default options in the remaining settings and select **Create**. Then wait for the deployment to succeed.
66
67
67
-

68
+

68
69
69
70
### Grant access to the event hub and get a connection string
70
71
@@ -140,7 +141,7 @@ Now that you have a stream of call events, you can create a Stream Analytics job
140
141
|Subscription |\<Your subscription\>| Select an Azure subscription where you want to create the job. |
141
142
|Resource group | MyASADemoRG | Select **Use existing** and enter a new resource-group name for your account. |
142
143
|Location | West US2 | Location where the job can be deployed. It's recommended to place the job and the event hub in the same region for best performance and so that you don't pay to transfer data between regions. |
143
-
|Hosting environment | Cloud | Stream Analytics jobs can be deployed to cloud or edge. Cloud allows you to deploy to Azure Cloud, and Edge allows you to deploy to an IoT Edge device. |
144
+
|Hosting environment | Cloud | Stream Analytics jobs can be deployed to cloud or edge. **Cloud** allows you to deploy to Azure Cloud, and **Edge** allows you to deploy to an IoT Edge device. |
144
145
|Streaming units | 1 | Streaming units represent the computing resources that are required to execute a job. By default, this value is set to 1. To learn about scaling streaming units, see [understanding and adjusting streaming units](stream-analytics-streaming-unit-consumption.md) article. |
145
146
146
147
4. Use default options on the remaining settings, select **Create**, and wait for the deployment to succeed.
@@ -162,33 +163,31 @@ The next step is to define an input source for the job to read data using the ev
162
163
|Input alias | CallStream | Provide a friendly name to identify your input. Input alias can contain alphanumeric characters, hyphens, and underscores only and must be 3-63 characters long. |
163
164
|Subscription |\<Your subscription\>| Select the Azure subscription where you created the event hub. The event hub can be in same or a different subscription as the Stream Analytics job. |
164
165
|Event hub namespace | asaTutorialEventHub | Select the event hub namespace you created in the previous section. All the event hub namespaces available in your current subscription are listed in the dropdown. |
165
-
|Event Hub name | MyEventHub | Select the event hub you created in the previous section. All the event hubs available in your current subscription are listed in the dropdown. |
166
-
|Event Hub policy name | MyPolicy | Select the event hub shared access policy you created in the previous section. All the event hubs policies available in your current subscription are listed in the dropdown. |
166
+
|Event hub name | MyEventHub | Select the event hub you created in the previous section. All the event hubs available in your current subscription are listed in the dropdown. |
167
+
|Event hub policy name | MyPolicy | Select the event hub shared access policy you created in the previous section. All the event hubs policies available in your current subscription are listed in the dropdown. |
167
168
168
169
4. Use default options on the remaining settings and select **Save**.
It is recommended to use a distinct consumer group for each Stream Analytics job. If no consumer group is specified, the Stream Analytics job uses the $Default consumer group. When a job contains a self-join or has multiple inputs, some inputs might be read by more than one reader downstream. This situation impacts the number of readers in a single consumer group.
175
+
We recommend that you use a distinct consumer group for each Stream Analytics job. If no consumer group is specified, the Stream Analytics job uses the $Default consumer group. When a job contains a self-join or has multiple inputs, some inputs later might be read by more than one reader. This situation affects the number of readers in a single consumer group.
175
176
176
-
Navigate to your Event Hubs Instance to add a new **Consumer group**.
177
+
To add a new consumer group:
177
178
178
-
1. In the **Entities** section of the Event Hubs Instance, select *Consumer Groups*.
179
+
1. In the Azure portal, go to your Event Hubs instance.
179
180
180
-
2. Select **+ Consumer group**.
181
+
1. In the left menu, under **Entities**, select **Consumer groups**.
181
182
182
-
3. Provide a specified name for your new consumer group.
1. In **Name**, enter a name for your new consumer group. For example, *MyConsumerGroup*.
186
+
187
+
1. Select **Create**.
188
+
189
+
:::image type="content" source="media/stream-analytics-real-time-fraud-detection/create-consumer-group.png" alt-text="Screenshot that shows creating a new consumer group.":::
190
190
191
-
192
191
## Configure job output
193
192
194
193
The last step is to define an output sink where the job can write the transformed data. In this tutorial, you output and visualize data with Power BI.
@@ -247,7 +246,7 @@ If you want to archive every event, you can use a pass-through query to read all
247
246
248
247
3. Select **Test query**.
249
248
250
-
The Stream Analytics job runs the query against the sample data from the input and displays the output at the bottom of the window. The results indicate that the Event Hub and the Streaming Analytics job are configured correctly.
249
+
The Stream Analytics job runs the query against the sample data from the input and displays the output at the bottom of the window. The results indicate that the Event Hubs and the Streaming Analytics job are configured correctly.
251
250
252
251
:::image type="content" source="media/stream-analytics-real-time-fraud-detection/sample-output-passthrough.png" alt-text="Sample output from test query":::
253
252
@@ -340,7 +339,7 @@ When you use a join with streaming data, the join must provide some limits on ho
340
339
341
340

342
341
343
-
## Embedding your Power BI Dashboard in a Web Application
342
+
## Embedding your Power BI Dashboard in a web application
344
343
345
344
For this part of the tutorial, you'll use a sample [ASP.NET](https://asp.net/) web application created by the Power BI team to embed your dashboard. For more information about embedding dashboards, see [embedding with Power BI](/power-bi/developer/embedding) article.
0 commit comments