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/discover-manage-assets/overview-manage-assets.md
+53-3Lines changed: 53 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -72,6 +72,8 @@ To learn more, see [Define assets and devices](concept-assets-devices.md).
72
72
73
73
Azure IoT Operations versions 1.1.x and before use *asset endpoints* to define the connection to assets in a similar way to how the current version uses *devices*. Devices offer greater flexibility and more capabilities than asset endpoints, such the ability to define multiple endpoints within a single device. The current version of Azure IoT Operations supports the use of both devices and asset endpoints, but the recommended approach is to use devices.
74
74
75
+
Assets associated with a device are known as *namespaced assets*, assets that are associated with an asset endpoint are simply known as *assets*. The following table shows the differences between devices and asset endpoints:
@@ -131,9 +133,57 @@ This screenshot shows the same thermostat asset in the Azure portal:
131
133
132
134
:::image type="content" source="media/overview-manage-assets/asset-portal.png" alt-text="A screenshot that shows the thermostat asset in the Azure portal.":::
133
135
134
-
And the final screenshot shows the same thermostat asset as a Kubernetes custom resource:
135
-
136
-
:::image type="content" source="media/overview-manage-assets/asset-kubernetes.png" alt-text="A screenshot that shows the thermostat asset as a Kubernetes custom resource.":::
136
+
And the final example shows the same thermostat asset as a Kubernetes custom resource:
137
+
138
+
```yaml
139
+
Name: thermostat
140
+
Namespace: azure-iot-operations
141
+
Labels: <none>
142
+
API Version: namespaces.deviceregistry.microsoft.com/v1beta1
143
+
Kind: Asset
144
+
Spec:
145
+
Attributes:
146
+
Batch: 102
147
+
Customer: Contoso
148
+
Equipment: Boiler
149
+
Is Spare: true
150
+
Location: Seattle
151
+
Datasets:
152
+
Data Points:
153
+
Data Point Configuration: {"publishingInterval":1000,"samplingInterval":1000,"queueSize":1,"keyFrameCount":0}
0 commit comments