Skip to content

Commit 664c948

Browse files
committed
Fix link
1 parent e185ff6 commit 664c948

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -62,14 +62,14 @@ After completing this flow, the Azure event hub is visible in the eventstream li
6262

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

65-
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 `mosquitto_sub` as described in [Verify data is flowing to MQTT broker](quickstart-configure.md#verify-data-is-flowing-to-mqtt-broker).
65+
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.
6666

6767
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.
6868

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

7171
>[!TIP]
72-
>If data has not arrived in your eventstream, you may want to check your event hub activity to [verify that it's receiving messages](quickstart-configure.md#verify-data-is-flowing-to-event-hubs). This will help you isolate which section of the flow to debug.
72+
>If data has not arrived in your eventstream, you may want to check your event hub activity to This will help you isolate which section of the flow to debug.
7373
7474
### Prepare KQL resources
7575

0 commit comments

Comments
 (0)