Skip to content

Commit b5eb35f

Browse files
authored
Merge pull request #281653 from kgremban/aiojuly-doe
DOE site updates for m1
2 parents 9384955 + 91115f1 commit b5eb35f

File tree

4 files changed

+23
-43
lines changed

4 files changed

+23
-43
lines changed

articles/iot-operations/discover-manage-assets/howto-manage-assets-remotely.md

Lines changed: 18 additions & 37 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Use the operations experience web UI or the Azure CLI to manage you
44
author: dominicbetts
55
ms.author: dobett
66
ms.topic: how-to
7-
ms.date: 03/01/2024
7+
ms.date: 07/23/2024
88
ms.custom:
99
- ignite-2023
1010
- devx-track-azurecli
@@ -75,7 +75,7 @@ az login
7575

7676
## Create an asset endpoint
7777

78-
By default, an Azure IoT Operations deployment includes a built-in OPC PLC simulator. To create an asset endpoint that uses the built-in OPC PLC simulator:
78+
An Azure IoT Operations deployment can include an optional built-in OPC PLC simulator. To create an asset endpoint that uses the built-in OPC PLC simulator:
7979

8080
# [Operations experience](#tab/portal)
8181

@@ -93,7 +93,6 @@ By default, an Azure IoT Operations deployment includes a built-in OPC PLC simul
9393
| Name | `opc-ua-connector-0` |
9494
| Connector for OPC UA URL | `opc.tcp://opcplc-000000:50000` |
9595
| User authentication | `Anonymous` |
96-
| Transport authentication | `Do not use transport authentication certificate` |
9796

9897
1. To save the definition, select **Create**.
9998

@@ -120,12 +119,12 @@ When the OPC PLC simulator is running, data flows from the simulator, to the con
120119

121120
The previous example uses the `Anonymous` authentication mode. This mode doesn't require a username or password.
122121

123-
# [Operations experience](#tab/portal)
124-
125122
To use the `UsernamePassword` authentication mode, complete the following steps:
126123

124+
# [Operations experience](#tab/portal)
125+
127126
1. Follow the steps in [Configure OPC UA user authentication with username and password](howto-configure-opcua-authentication-options.md#configure-username-and-password-authentication) to add secrets for username and password in Azure Key Vault, and project them into Kubernetes cluster.
128-
2. In the operations experience, select **Username & password** for the **User authentication** field to configure the asset endpoint to use these secrets. Then enter the following values for the **Username reference** and **Password reference** fields:
127+
2. In the operations experience, select **Username password** for the **User authentication** field to configure the asset endpoint to use these secrets. Then enter the following values for the **Username reference** and **Password reference** fields:
129128

130129
| Field | Value |
131130
| --- | --- |
@@ -134,8 +133,6 @@ To use the `UsernamePassword` authentication mode, complete the following steps:
134133

135134
# [Azure CLI](#tab/cli)
136135

137-
To use the `UsernamePassword` authentication mode, complete the following steps:
138-
139136
1. Follow the steps in [Configure OPC UA user authentication with username and password](howto-configure-opcua-authentication-options.md#configure-username-and-password-authentication) to add secrets for username and password in Azure Key Vault, and project them into Kubernetes cluster.
140137

141138
1. Use a command like the following example to create your asset endpoint:
@@ -146,29 +143,6 @@ To use the `UsernamePassword` authentication mode, complete the following steps:
146143
147144
---
148145
149-
### Configure an asset endpoint to use a transport authentication certificate
150-
151-
To configure the asset endpoint to use a transport authentication certificate, complete the following steps:
152-
153-
# [Operations experience](#tab/portal)
154-
155-
1. Follow the steps in [configure mutual trust](howto-configure-opcua-certificates-infrastructure.md#configure-the-trusted-certificates-list) to add a transport certificate and private key to Azure Key Vault, and project them into Kubernetes cluster.
156-
2. In the operations experience, select **Use transport authentication certificate** for the **Transport authentication** field and enter the certificate thumbprint.
157-
158-
# [Azure CLI](#tab/cli)
159-
160-
1. Follow the steps in [configure mutual trust](howto-configure-opcua-certificates-infrastructure.md#configure-the-trusted-certificates-list) to add a transport certificate and private key to Azure Key Vault, and project them into Kubernetes cluster.
161-
162-
1. Use a command like the following example to create your asset endpoint:
163-
164-
```azurecli
165-
az iot ops asset endpoint create --name opc-ua-connector-0 --target-address opc.tcp://opcplc-000000:50000 -g {your resource group name} --cluster {your cluster name} --username-ref "aio-opc-ua-broker-user-authentication/username" --password-ref "aio-opc-ua-broker-user-authentication/password"
166-
```
167-
168-
To learn more, see [az iot ops asset](/cli/azure/iot/ops/asset).
169-
170-
---
171-
172146
## Add an asset, tags, and events
173147
174148
# [Operations experience](#tab/portal)
@@ -182,15 +156,14 @@ To add an asset in the operations experience:
182156
> [!TIP]
183157
> You can use the filter box to search for assets.
184158
185-
Select **Create asset**.
159+
1. Select **Create asset**.
186160
187161
1. On the asset details screen, enter the following asset information:
188162
189-
- Asset name
190163
- Asset endpoint. Select your asset endpoint from the list.
164+
- Asset name
191165
- Description
192166
193-
194167
1. Configure the set of properties that you want to associate with the asset. You can accept the default list of properties or add your own. The following properties are available by default:
195168
196169
- Manufacturer
@@ -203,6 +176,7 @@ To add an asset in the operations experience:
203176
- Documentation URI
204177
205178
:::image type="content" source="media/howto-manage-assets-remotely/create-asset-details.png" alt-text="Screenshot that shows how to add asset details in the operations experience.":::
179+
206180
1. Select **Next** to go to the **Add tags** page.
207181
208182
### Add individual tags to an asset
@@ -312,9 +286,6 @@ Now you can define the events associated with the asset. To add OPC UA events:
312286
- Event name (Optional). This value is the friendly name that you want to use for the event. If you don't specify an event name, the event notifier is used as the event name.
313287
- Observability mode (Optional) with following choices:
314288
- None
315-
- Gauge
316-
- Counter
317-
- Histogram
318289
- Log
319290
- Queue size. You can override the default value for this tag.
320291

@@ -452,6 +423,16 @@ Whenever you make a change to asset in the operations experience, you see a noti
452423

453424
:::image type="content" source="media/howto-manage-assets-remotely/portal-notifications.png" alt-text="A screenshot that shows the notifications in the operations experience.":::
454425

426+
## View activity logs
427+
428+
In the operations experience, you can view activity logs for each instance or each resource in an instance.
429+
430+
To view activity logs at the instance level, select the **Activity logs** tab. You can use the **Timespan** and **Resource type** filters to customize the view.
431+
432+
:::image type="content" source="./media/howto-manage-assets-remotely/view-instance-activity-logs.png" alt-text="A screenshot that shows the activity logs for an instance in the operations experience.":::
433+
434+
To view activity logs as the resource level, select the resource that you want to inspect. This resource can be an asset, asset endpoint, or data pipeline. In the resource overview, select **View activity logs**. You can use the **Timespan** filter to customize the view.
435+
455436
## Related content
456437

457438
- [Connector for OPC UA overview](overview-opcua-broker.md)
91.7 KB
Loading
13 KB
Loading

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

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.author: dobett
66
ms.topic: quickstart
77
ms.custom:
88
- ignite-2023
9-
ms.date: 02/19/2024
9+
ms.date: 07/23/2024
1010

1111
#CustomerIntent: As an OT user, I want to create assets in Azure IoT Operations so that I can subscribe to asset data points, and then process the data before I send it to the cloud.
1212
---
@@ -25,7 +25,7 @@ In this quickstart, you use the operations experience web UI to create your asse
2525

2626
## Prerequisites
2727

28-
Complete [Quickstart: Run Azure IoT Operations Preview in Github Codespaces with K3s](quickstart-deploy.md) before you begin this quickstart.
28+
Complete [Quickstart: Run Azure IoT Operations Preview in GitHub Codespaces with K3s](quickstart-deploy.md) before you begin this quickstart.
2929

3030
To sign in to the operations experience, you need a work or school account in the tenant where you deployed Azure IoT Operations. If you're currently using a Microsoft account (MSA), you need to create a Microsoft Entra ID with at least contributor permissions for the resource group that contains your **Kubernetes - Azure Arc** instance. To learn more, see [Known Issues > Create Entra account](../troubleshoot/known-issues.md#known-issues-azure-iot-operations-preview).
3131

@@ -57,7 +57,7 @@ Select the instance where you deployed Azure IoT Operations in the previous quic
5757
5858
## Add an asset endpoint
5959

60-
When you deployed Azure IoT Operations, you chose to include a built-in OPC PLC simulator. In this step, you add an asset endpoint that enables you to connect to the OPC PLC simulator.
60+
When you deployed Azure IoT Operations in the previous article, you included a built-in OPC PLC simulator. In this step, you add an asset endpoint that enables you to connect to the OPC PLC simulator.
6161

6262
To add an asset endpoint:
6363

@@ -72,7 +72,6 @@ To add an asset endpoint:
7272
| Asset endpoint name | `opc-ua-connector-0` |
7373
| OPC UA server URL | `opc.tcp://opcplc-000000:50000` |
7474
| User authentication mode | `Anonymous` |
75-
| Transport authentication | `Do not use transport authentication certificate` |
7675

7776
1. To save the definition, select **Create**.
7877

@@ -131,8 +130,8 @@ To create an asset, select **Create asset**. Then enter the following asset info
131130

132131
| Field | Value |
133132
| --- | --- |
134-
| Asset name | `thermostat` |
135133
| Asset Endpoint | `opc-ua-connector-0` |
134+
| Asset name | `thermostat` |
136135
| Description | `A simulated thermostat asset` |
137136

138137
Remove the existing **Custom properties** and add the following custom properties. Be careful to use the exact property names, as the Power BI template in a later quickstart queries for them:
@@ -160,7 +159,7 @@ Add two OPC UA tags on the **Add tags** page. To add each tag, select **Add tag
160159

161160
The **Observability mode** is one of the following values: `none`, `gauge`, `counter`, `histogram`, or `log`.
162161

163-
You can override the default sampling interval and queue size for each tag.
162+
You can select **Manage default settings** to change the default sampling interval and queue size for each tag.
164163

165164
:::image type="content" source="media/quickstart-add-assets/add-tag.png" alt-text="Screenshot of Azure IoT Operations add tag page.":::
166165

0 commit comments

Comments
 (0)