Skip to content

Commit 852f6f0

Browse files
committed
Fixes
1 parent 4e99a74 commit 852f6f0

7 files changed

Lines changed: 13 additions & 4 deletions

File tree

articles/iot-operations/discover-manage-assets/howto-connect-kafka.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ To connect to a Kafka source, you combine:
2222

2323
The following diagram illustrates this architecture:
2424

25-
:::image type="content" source="media/howto-connect-kafka/kafka.svg" alt-text="Diagram that shows the architecture of the solution." lightbox="media/howto-connect-kafka/kafka.png":::
25+
:::image type="content" source="media/howto-connect-kafka/kafka.svg" alt-text="Diagram that shows the architecture of the solution." lightbox="media/howto-connect-kafka/kafka.png" border="false":::
2626

2727
Messages enter from the Kafka source, such as an Azure Event Hubs namespace, and are ingested into Azure IoT Operations through a data flow with a Kafka source endpoint. The data flow routes messages to topics in the internal MQTT broker. The connector for MQTT detects the topics in the MQTT broker and lets you create assets based on the topic names. Each asset can be configured to route data to specific topics in the MQTT broker. You can then perform any routing and custom processing to the messages.
2828

articles/iot-operations/discover-manage-assets/howto-control-opc-ua.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -430,5 +430,6 @@ For example, the DTDL model for the `call` actions the sample uses looks like th
430430

431431
## Related content
432432

433+
- [Enable and run management actions](howto-use-management-actions.md)
433434
- [Manage asset and device configurations](overview-manage-assets.md)
434435
- [Connector for OPC UA overview](overview-opc-ua-connector.md)

articles/iot-operations/discover-manage-assets/howto-use-management-actions.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ This article explains how to enable management actions, execute actions on asset
3030

3131
## Enable management actions
3232

33-
For a complete end-to-end setup script that creates the Event Grid namespace, device, asset, and enables management actions in one step, see the [management actions quickstart](https://github.com/Azure/azure-iot-ops-cli-extension/blob/mgmt_actions_quickstart/scripts/mgmt-actions/README.md) in the CLI extension repository.
33+
For a complete end-to-end setup script that creates the Event Grid namespace, device, asset, and enables management actions in one step, see the [management actions quickstart](https://github.com/Azure/azure-iot-ops-cli-extension/blob/v2.4.0/scripts/mgmt-actions/README.md) in the CLI extension repository.
3434

3535
The `az iot ops mgmt-actions enable` command in the quickstart script provisions the management actions infrastructure on your Azure IoT Operations instance. The command creates the following resources:
3636

@@ -110,7 +110,7 @@ For more information about how to define action types in an asset's management g
110110

111111
Management actions use two data flows and Azure Event Grid to connect a cloud client to a connector running in the Azure IoT Operations cluster. The following sections describe the request and response message flows in detail.
112112

113-
:::image type="content" source="media/howto-use-management-actions/architecture.svg" alt-text="Diagram that shows the architecture of management actions request and response flows through Event Grid, data flows, MQTT broker, and connector to a southbound asset." lightbox="media/howto-use-management-actions/architecture.png":::
113+
:::image type="content" source="media/howto-use-management-actions/architecture.svg" alt-text="Diagram that shows the architecture of management actions request and response flows through Event Grid, data flows, MQTT broker, and connector to a southbound asset." lightbox="media/howto-use-management-actions/architecture.png" border="false":::
114114

115115
### Request flow
116116

articles/iot-operations/discover-manage-assets/howto-use-mqtt-connector.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -215,6 +215,7 @@ To add a management group and define actions for it:
215215
When you invoke the action, the connector publishes the action payload to the **Target URI** topic on the device's inbound endpoint. A downstream subscriber on that topic receives the message and can act on it.
216216

217217
For background on how management groups and actions work across connectors, see:
218+
- [Enable and run management actions](howto-use-management-actions.md)
218219
- [Control OPC UA servers](howto-control-opc-ua.md) — explains the action invocation pattern and the MQTT RPC protocol used to trigger actions.
219220
- [Manage and control the camera](howto-use-onvif-connector.md#manage-and-control-the-camera) — shows how a similar pattern is used for the connector for ONVIF.
220221

articles/iot-operations/discover-manage-assets/howto-use-onvif-connector.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -308,4 +308,8 @@ The [Azure IoT Operations connector for ONVIF PTZ Demo](https://github.com/Azure
308308
- Use the media asset definition to retrieve a profile token from the camera's media service.
309309
- Use the profile token when you use the camera's PTZ capabilities control its position and orientation.
310310

311-
The sample application uses the Azure IoT Operations MQTT broker to send commands to interact with the connector for ONVIF. To learn more, see [Publish and subscribe MQTT messages using MQTT broker](../manage-mqtt-broker/overview-broker.md).
311+
The sample application uses the Azure IoT Operations MQTT broker to send commands to interact with the connector for ONVIF.
312+
313+
To learn more, see:
314+
- [Enable and run management actions](howto-use-management-actions.md)
315+
- [Publish and subscribe MQTT messages using MQTT broker](../manage-mqtt-broker/overview-broker.md).
-3.6 KB
Loading

articles/iot-operations/discover-manage-assets/overview-manage-assets.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -154,6 +154,9 @@ The following table summarizes which data types each connector supports.
154154
| SSE | Yes | Yes | | |
155155
| MQTT | Yes | | Yes | |
156156

157+
> [!TIP]
158+
> To learn more about how management groups and actions work across connectors, see [Enable and run management actions](howto-use-management-actions.md).
159+
157160
#### Discovery
158161

159162
You can use Akri services to automatically discover physical devices and assets. Akri services also help operational technology (OT) users set up devices and assets in the operations experience web UI. The connectors described earlier all use the framework that Akri services provide to implement their core capabilities.

0 commit comments

Comments
 (0)