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-edge/how-to-monitor-iot-edge-deployments.md
+36-9Lines changed: 36 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,11 +24,7 @@ Successful deployments require monitoring the following information:
24
24
25
25
* Versions of deployed modules.
26
26
27
-
Both devices and modules have similar data, such as connectivity, so values are obtained according the device ID or the module ID.
28
-
29
-
Automatic deployments are deployments made to devices that satisfy a target condition. Target conditions are configured using tags specified in the device twin.
30
-
31
-
Layered deployments have addition criterion such as to overwrite a module if a particular criterion is satisfied. This criteria is configured by adding desired properties in the module twin.
27
+
Both devices and modules have similar data, such as connectivity, so values are obtained according the device ID or the module ID. For an overview of the IoT Edge runtime modules and their properties, see [Properties of the IoT Edge agent and IoT Edge hub module twins](module-edgeagent-edgehub.md).
32
28
33
29
The IoT Hub service collects the data reported by device and module twins and provides aggregated counts of the various states that devices may have. The IoT Hub service organizes this data into four groups of metrics:
34
30
@@ -72,15 +68,46 @@ To view the details of a deployment and monitor the devices running it, use the
If you developed custom code modules, such as described in [Use Visual Studio 2019 to develop and debug modules for Azure IoT Edge](how-to-visual-studio-develop-module.md), you can monitor their values by defining custom metrics. You can also add, delete, and edit properties in the module twin after the module has been deployed to an IoT Edge device.
74
+
75
+
To define and edit properties for a deployed module:
76
+
77
+
1. In your IoT hub, select **IoT Edge** from the left pane menu.
78
+
1. Select the device with the module you want to edit.
79
+
1. On the **Modules** tab, select the module.
80
+
1. On the module details page, on the upper menu bar select **Module Identity Twin**.
81
+
82
+

83
+
84
+
### Define targets
85
+
86
+
You can target the devices to receive the deployment by specifying target conditions when you create or modify a deployment. To define a custom metric:
87
+
88
+
1. In your IoT hub, select **IoT Edge** from the left pane menu.
89
+
90
+
* If you are creating a new deployment, select **Create Deployment** from the upper menu bar. As part of completing the wizard, select the **Target Devices** tab.
91
+
92
+
* If you are modifying a deployment, select the **IoT Edge deployments** tab and select the deployment you want to configure. Select the **Target Condition** tab.
93
+
94
+
1. Define a target condition, using the example syntax as a guide.
95
+
96
+

97
+
75
98
### Define a custom metric
76
99
77
-
You can define custom metrics in the Azure portal when you create a deployment.
100
+
You can define custom metrics in the Azure portal when you create or modify a deployment. To define a custom metric:
78
101
79
102
1. In your IoT hub, select **IoT Edge** from the left pane menu.
80
-
1. Select **Create Deployment** from the upper menu bar.
81
-
1. Complete the wizard, and on the **Metrics** tab you can define a custom metric using the example syntax as a guide.
82
103
83
-

104
+
* If you are creating a new deployment, select **Create Deployment** from the upper menu bar. As part of completing the wizard, select the **Metrics** tab.
105
+
106
+
* If you are modifying a deployment, select the **IoT Edge deployments** tab and then select the deployment you want to configure. Select the **Metrics** tab.
107
+
108
+
1. Define a custom metric, using the example syntax as a guide.
109
+
110
+

0 commit comments