Back then, I had to do some magic with both a C# IoT Edge module, a custom NodeJS docker container, and a Docker network to get it running.
Since then, a lot has changed. Microsoft already released a ton of new features. a And there is still more to come regarding the Azure IoT platform.
But that awkward local dashboard solution was nagging me. A few months ago, Microsoft introduced a NodeJS module as a first-class citizen for IoT Edge modules.
So it was time to pick up the gauntlet and use NodeJS for this awesome local IoT Edge dashboard:
#tldr; If you like to dig into the code, zip it, clone it, extend it or even make a pull request, I made this project open source. If you only want to use it the easy-going way, pull it from docker eg. ‘svelde/localdashboard:1.0.1-amd64’.
At this moment, only Linux containers are supported. It is tested both on Windows and Ubuntu as host OS.
Interested in this module? Let’s see how you can use it.
Microsoft is serious about IoT Edge. Azure IoT Edge is now GA for a few months and just last week the version was bumped up to 1.0.1.
The same effort is put into Edge modules. Microsoft provides several modules for different protocols like OPC-UA and Modbus.
In the past I already wrote a couple of times about Modbus TCP in IoT Edge. It’s easy to use and reliable. The Microsoft Modbus module is already available in GA. And I even noticed a reference to “docker pull mcr.microsoft.com/azureiotedge/modbus:1.0”.
If you look deeper into the documentation, you can see that the module supports Modbus RTU too!
It’s always good to learn about other protocols so I arranged some hardware and started a journey.
Azure IoT Edge is an interesting platform for Edge computing. It opens up a lot of new scenarios for local computing as an extension of the Azure cloud. And the combination is both secure and flexible due to the usage of open (security) standards.
But it’s still in Public Preview so once in a while things go sour. Either no messages arrive at in the cloud or local logic is not executed. So this means you have to log into your Edge device (remember to always have a backup plan) and check out the local logging.
But what if I could check out the logging right within Azure?
I came across this Github gem to make Azure IoT Edge local logs available in Azure! And it only takes 15 minutes or less.
“This repository provides an Azure IoT Edge module that can be used to send container logs from other modules on the edge device, including the edge runtime, securely to Azure Log Analytics in the cloud. “
Microsoft has a great solution for persisting your local data collected by the IoT Edge. It’s up to you to get the data in and out of your database. But you have a convenient way of storing your precious information into some kind of persistent storage.
As seen in my previous blog, it’s not that hard to deploy from the cloud and administer your SQL database locally.
But how persistent is your database actually? Can you trust Docker for taking care of your data?