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/iot-operations/connect-to-cloud/howto-schema-registry.md
+16-21Lines changed: 16 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: Learn how to install schema registry on your cluster and create mes
4
4
author: kgremban
5
5
ms.author: kgremban
6
6
ms.topic: how-to
7
-
ms.date: 08/03/2024
7
+
ms.date: 09/23/2024
8
8
9
9
#CustomerIntent: As an operator, I want to understand how I can use message schemas to filter and transform messages.
10
10
---
@@ -13,34 +13,29 @@ ms.date: 08/03/2024
13
13
14
14
Use schema registry to store and synchronize message schemas across the cloud and edge. Dataflows and other edge services use message schemas to filter and transform messages as they're routed across your industrial edge scenario.
15
15
16
-
## Create schema registry resources in Azure
16
+
Schemas are documents that describe data to enable processing and contextualization.
17
17
18
-
1. Create a storage account with hierarchical namespace enabled.
18
+
Message schemas describe the format of a message and its contents.
* An Azure IoT Operations instance deployed to a cluster along with a schema registry. For more information, see [Deployment details](../deploy-iot-ops/overview-deploy.md).
1. In the [operations experience](https://iotoperations.azure.com), select your site and Azure IoT Operations instance.
37
31
38
-
1.Verify that schema registry pods are running by using the `kubectl get pods` command.
32
+
1.Select **Dataflows** > **Create dataflow**.
39
33
40
-
```bash
41
-
kubectl get pods -n azure-iot-operations
42
-
```
34
+
1. Select **Source** > **MQTT**.
43
35
44
-
## Upload message schemas in the operations experience
36
+
1. Select **Upload**.
37
+
38
+
:::image type="content" source="./media/howto-schema-registry/upload-schema.png" alt-text="Screenshot that shows uploading a message schema in the operations experience portal.":::
39
+
40
+
1. Browse to your message schema JSON file and select **Open**.
Copy file name to clipboardExpand all lines: articles/iot-operations/connect-to-cloud/overview-dataflow.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -59,13 +59,13 @@ The configuration is specified by using Kubernetes CRDs. Based on this configura
59
59
60
60
By using dataflows, you can efficiently manage your data paths. You can ensure that data is accurately sent, transformed, and enriched to meet your operational needs.
61
61
62
-
## Support for schema registry
62
+
## Schema registry
63
63
64
64
Schema registry, a feature provided by Azure Device Registry Preview, is a synchronized repository in the cloud and at the edge. The schema registry stores the definitions of messages coming from edge assets, and then exposes an API to access those schemas at the edge. Southbound connectors like the OPC UA connector can create message schemas and add them to the schema registry or customers can upload schemas to the operations experience web UI.
65
65
66
66
Dataflows uses messages schemas at both the source and destination points. For sources, message schemas can work as filters to identify the specific messages that you want to capture for a dataflow. For destinations, message schemas help to transform the message into the format expected by the destination endpoint.
67
67
68
-
For more information, see [Define message schemas](./howto-schema-registry.md).
68
+
For more information, see [Create message schemas](./howto-schema-registry.md).
0 commit comments