Skip to content

Commit 9ebcfdf

Browse files
committed
Screenshot updates
1 parent 9aec86f commit 9ebcfdf

File tree

3 files changed

+53
-3
lines changed

3 files changed

+53
-3
lines changed
-10.3 KB
Loading
2.82 KB
Loading

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

Lines changed: 53 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -72,6 +72,8 @@ To learn more, see [Define assets and devices](concept-assets-devices.md).
7272

7373
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.
7474

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:
76+
7577
| Azure IoT Operations version | Devices supported | Asset endpoints supported |
7678
|-----------------------------|-------------------|--------------------------|
7779
| v1.1.x and before | No | Yes |
@@ -131,9 +133,57 @@ This screenshot shows the same thermostat asset in the Azure portal:
131133

132134
:::image type="content" source="media/overview-manage-assets/asset-portal.png" alt-text="A screenshot that shows the thermostat asset in the Azure portal.":::
133135

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}
154+
Data Source: ns=3;s=SpikeData
155+
Name: temperature
156+
Data Source: default
157+
Dataset Configuration: {"publishingInterval":1000,"samplingInterval":1000,"queueSize":1,"keyFrameCount":0}
158+
Destinations:
159+
Configuration:
160+
Qos: Qos1
161+
Retain: Keep
162+
Topic: /
163+
Target: Mqtt
164+
Name: default
165+
Default Datasets Configuration: {"publishingInterval":1000,"samplingInterval":1000,"queueSize":1,"keyFrameCount":0}
166+
Default Events Configuration: {"publishingInterval":1000,"samplingInterval":1000,"queueSize":1,"keyFrameCount":0}
167+
Device Ref:
168+
Device Name: opc-ua-connector
169+
Endpoint Name: opc-ua-connector-0
170+
Display Name: thermostat
171+
Enabled: true
172+
Events:
173+
Destinations:
174+
Configuration:
175+
Qos: Qos1
176+
Retain: Keep
177+
Topic: /
178+
Target: Mqtt
179+
Event Configuration: {"publishingInterval":1000,"samplingInterval":1000,"queueSize":1,"keyFrameCount":0}
180+
Event Notifier: default
181+
Name: default
182+
External Asset Id: 0000aaaa-11bb-cccc-dd22-eeeeee333333
183+
Uuid: 0000aaaa-11bb-cccc-dd22-eeeeee333333
184+
Version: 1
185+
Events: <none>
186+
```
137187
138188
### Automatic asset discovery
139189

0 commit comments

Comments
 (0)