Skip to content

Commit 8456734

Browse files
Merge pull request #283597 from baanders/release-aio-july-updates
AIO quickstart 4, Clarity updates
2 parents fd7b37e + db4beb3 commit 8456734

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

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

Lines changed: 3 additions & 3 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: 08/01/2024
9+
ms.date: 08/05/2024
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
---
@@ -69,7 +69,7 @@ Follow these steps to check your work so far, and make sure data is flowing into
6969

7070
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 to the MQTT broker. You can verify this part of the flow using mqttui as described in [Verify data is flowing](quickstart-add-assets.md#verify-data-is-flowing).
7171

72-
1. Wait a few minutes for data to propagate. Then, in the eventstream live view, refresh the **Data preview**. You should see JSON data from the simulator begin to appear in the table.
72+
1. Wait a few minutes for data to propagate. Then, in the eventstream live view, select the *AzureEventHub* source and refresh the **Data preview**. You should see JSON data from the simulator begin to appear in the table.
7373

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

@@ -249,6 +249,6 @@ This completes the final step in the quickstart flow for using Azure IoT Operati
249249
250250
## Clean up resources
251251
252-
If you're not going to continue to use this deployment, delete the Kubernetes cluster where you deployed Azure IoT Operations. In Azure, remove the Azure resource group that contains the cluster and your event hub.
252+
If you're not going to continue to use this deployment, delete the Kubernetes cluster where you deployed Azure IoT Operations. In Azure, remove the Azure resource group that contains the cluster and your event hub. If you used Codespaces for these quickstarts, delete your Codespace from GitHub.
253253
254254
You can also delete your Microsoft Fabric workspace and/or all the resources within it associated with this quickstart, including the eventstream, Eventhouse, and Real-Time Dashboard.

0 commit comments

Comments
 (0)