Skip to content

Commit f7a1977

Browse files
committed
Clarity updates
1 parent 43dde24 commit f7a1977

File tree

1 file changed

+8
-6
lines changed

1 file changed

+8
-6
lines changed

articles/iot-operations/get-started-end-to-end-sample/quickstart-get-insights.md

Lines changed: 8 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.author: baanders
66
ms.topic: quickstart
77
ms.custom:
88
- ignite-2023
9-
ms.date: 01/27/2025
9+
ms.date: 01/28/2025
1010

1111
#CustomerIntent: As an OT user, I want to create a visual report for my processed OPC UA data that I can use to analyze and derive insights from it.
1212
---
@@ -37,7 +37,9 @@ In this section, you set up a Microsoft Fabric *eventstream* to connect your eve
3737

3838
In this section, you create an eventstream that's used to bring your data from Event Hubs into Microsoft Fabric Real-Time Intelligence, and eventually into a KQL database.
3939

40-
Start by navigating to the [Real-Time hub in Microsoft Fabric](https://app.powerbi.com/workloads/oneriver/hub?experience=fabric-developer). Add your event hub as a data source for a new eventstream (for detailed instructions, see [Get events from Azure Event Hubs into Real-time hub](/fabric/real-time-hub/add-source-azure-event-hubs#microsoft-sources-page)). As you add the data source, keep the following notes in mind:
40+
Start by navigating to the [Real-Time hub in Microsoft Fabric](https://app.powerbi.com/workloads/oneriver/hub?experience=fabric-developer).
41+
42+
Add your event hub as a data source for a new eventstream (for detailed instructions, see [Get events from Azure Event Hubs into Real-time hub](/fabric/real-time-hub/add-source-azure-event-hubs#microsoft-sources-page)). As you add the data source, keep the following notes in mind:
4143

4244
* For **Azure Event Hub Key**, use the default selection (*RootManageSharedAccessKey*).
4345
* You can edit the **Eventstream name** to something friendly in the **Stream details** pane.
@@ -54,14 +56,14 @@ After connecting the eventstream, use the **Open Eventstream** button to see it
5456

5557
Follow these steps to check your work so far, and make sure data is flowing into the eventstream.
5658

57-
1. Start your cluster where you deployed Azure IoT Operations in earlier quickstarts. The OPC PLC simulator you deployed with your Azure IoT Operations instance should begin running and sending data. You can [verify that your event hub is receiving messages](quickstart-configure.md#verify-data-is-flowing-to-event-hubs) in the Azure portal.
59+
1. Start your cluster where you deployed Azure IoT Operations in earlier quickstarts. The OPC PLC simulator you deployed with your Azure IoT Operations instance should begin running and sending data. You can confirm this by [verifying that your event hub is receiving messages](quickstart-configure.md#verify-data-is-flowing-to-event-hubs) in the Azure portal.
5860

59-
1. Wait a few minutes for data to propagate. Then, in the eventstream live view, select the Azure event hub source and refresh the **Data preview**. You should see JSON data from the simulator begin to appear in the table.
61+
1. Wait a few minutes for data to propagate. Then, in the eventstream live view, select the eventstream source and refresh the **Data preview**. You should see JSON data from the simulator begin to appear in the table.
6062

6163
:::image type="content" source="media/quickstart-get-insights/source-added-data.png" alt-text="Screenshot of the eventstream with data from the AzureEventHub source.":::
6264

6365
>[!TIP]
64-
>If data hasn't arrived in your eventstream, you may want to check your event hub activity to help you isolate which section of the flow to debug.
66+
>If data isn't arriving in your eventstream, you may want to check your event hub activity to help you isolate which section of the flow to debug.
6567
6668
### Prepare KQL resources
6769

@@ -80,7 +82,7 @@ In this section, you create a KQL database in your Microsoft Fabric workspace to
8082
| EnergyUse | decimal |
8183
| Timestamp | datetime |
8284

83-
1. After the *OPCUA* table has been created, select it and use the **Query with code** button to open any sample query in a new query window for the table.
85+
1. After the *OPCUA* table is created, select it and use the **Query with code** button to open any sample query in a new query window for the table.
8486

8587
:::image type="content" source="media/quickstart-get-insights/query-with-code.png" alt-text="Screenshot showing the Query with code button.":::
8688

0 commit comments

Comments
 (0)