IoT Edge Remote Monitoring Lab

Learn how to monitor IoT Edge devices' built-in metrics with Azure Monitor.

You'll need Azure Cloud Shell for this lab with an active Azure subscription.

Perform the following steps in the Azure Cloud Shell environment.

Select Bash from the top left as the environment for your cloud shell.
Add the Azure IoT extension to the cloud shell instance.
```
az extension add --name azure-iot
```
If you get ModuleNotFoundError, please retry after removing the old extension using az extension remove –name azure-cli-iot-ext
Create a resource group to hold the cloud infrastructure you'll use for the lab.

Use only lowercase alphabets and numbers in your unique string

# Pick a unique string to append to your resources
export UNIQUESTRING=replace-with-lastname-for-example   
export RGLOC=westus2   

az group create \
--name iotlab-resources-$UNIQUESTRING \
--location $RGLOC

Perform these steps in the cloud shell environment.

Create an IoT Hub

az iot hub create \
--resource-group iotlab-resources-$UNIQUESTRING \
--name iotlab-hub-$UNIQUESTRING \
--sku S1 \
--partition-count 2

az iot hub device-identity create \
--hub-name iotlab-hub-$UNIQUESTRING \
--device-id edge-device-$UNIQUESTRING \
--edge-enabled

We'll use an Azure VM as a virtual edge "device" and associate it with the device identity created in the previous step.

Setup an SSH key to login to the VM

ssh-keygen -m PEM -t rsa -b 4096 -q -f ~/.ssh/id_lab -N ""

Provision a VM and associate with edge device identity

# Set environment variable
export CONNSTR=$(az iot hub device-identity show-connection-string \
  --device-id edge-device-$UNIQUESTRING \
  --hub-name iotlab-hub-$UNIQUESTRING \
  -o tsv)   

# Deploy VM
az group deployment create \
  --name edgeVm \
  --resource-group iotlab-resources-$UNIQUESTRING \
  --template-uri "https://aka.ms/iotedge-vm-deploy-lab" \
  --parameters location=$RGLOC \
  --parameters dnsLabelPrefix=iotedge-vm-$UNIQUESTRING \
  --parameters adminUsername='azureuser' \
  --parameters deviceConnectionString=$CONNSTR \
  --parameters authenticationType='sshPublicKey' \
  --parameters adminPasswordOrKey="$(< ~/.ssh/id_lab.pub)" | \
    jq .properties.outputs

Note the ssh command from the value key in previous command's output and use it to login to the VM. For example ssh -i ~/.ssh/id_lab azureuser@iotedge-vm-xyz.westus2.cloudapp.azure.com.
It can take about 2 minutes for the VM to complete provisioning, enter watch sudo iotedge list in the VM's bash shell and wait for the edgeAgent module to be reported as running. It is expected to see "command not found" initially. Ctrl+c returns you to the VM's shell.
Type exit in the VM's SSH shell to return the cloud shell environment

Navigate to the Azure Portal using the following url: https://aka.ms/edgemon-portal
Go to the portal page for IoT Hub created in the prior step. If you are having trouble finding it, enter the unique string you chose in the search bar after ensuring the subscription you are using is selected.
Select the IoT Edge ToC item and click on the device you created earlier.
On the device details page, click the Set modules button on the top left
Click on + Add and select + IoT Edge Module
In the Add IoT Edge Module screen, enter tempSensor for Module name and mcr.microsoft.com/azureiotedge-simulated-temperature-sensor:1.0.10 for Image URI. Then click the Add button at the bottom.
Back on the Set Modules screen, click Review + create followed by Create to set the workload.
In a few seconds, you should see the tempSensor module listed in output of sudo iotedge list on the VM created in the previous step.

Now, to monitor the edge device we'll add the Azure Monitor IoT Edge module.

Note the Resource ID of the IoT Hub from the Properties ToC item:
Select the IoT Edge ToC item and click on the device you created earlier.
On the device details page, click the Set modules button on the top left
Click on + Add and select + IoT Edge Module
In the Add IoT Edge Module pane, enter azmonitor for Module name and mcr.microsoft.com/azuremonitor/containerinsights/ciprod:iot-0.1.3.2-amd64 for Image URI.

On the same pane, click on the Environment Variables tab and add two variables with names and values noted below:

`HubResourceID`	Value noted in Step 1
`LogAnalyticsWorkspaceId`	`80868412-0fe2-4c0f-af0d-d4a9dfbb5f24`
`LogAnalyticsSharedKey`	`B22uotMZQfOaIiWe9LIe72NPlOwEP3senQc9u1QhH4aHsJsJ3+rbjrY4qv1cL17V1UeGSl/fOXuFNi4NJDhBNA==`

(The last two characters of the shared key are ==)

Click the Add button at the bottom to confirm module settings, followed by Review + create and Create on the Set Modules screen.
In a few seconds, you should see the azmonitor module listed in output of sudo iotedge list on the VM created earlier.

In a few minutes, you can visualize detailed metrics from the device right in the IoT Hub portal page with Azure Monitor Workbooks!

Check out this 5-min video demo that explores the visualizations enabled using Azure Monitor Workbooks.

Congratulations on completing the lab! If you are interested in exploring more about this feature including how to monitor metrics from your custom module using this solution and at-scale alerting, please sign up for the preview at https://aka.ms/edgemon-intake