Azure IoT Edge
Azure IoT Edge moves analytics and logic out of the cloud and onto your on-premises devices. Using a cloud interface, you can deploy either Azure service logic or your own code to devices without having to physically access them. And offline capabilities mean that you can extract business insights anywhere, without worrying about maintaining constant communication with a cloud service.
More details about the services are available in the documentation.
-
Removing unused modules from IoT Edge devices
I am successfully able to add and remove custom modules from a deployment. However, I notice that modules that I remove through a deployment, remain on the device, occupying space. So at some point, the device's storage will get filled up with junk (outdated or unnecessary modules), leading to a system crash.
This is the response I received from Microsoft - "Thanks for your feedback @baharw . That is by design - you can easily integrate a direct method for example that would be responsible to remove all unused docker images on your edge device. I nevertheless suggest that you…
104 votes -
Code sample for identity translation pattern.
If the development team is busy, some guidance on how does the module(who understand native protocols and gives device identity) receive the connection string will be helpful. Hard coding connection strings is not is not an option.
96 votes -
Make IoT-Edge (V2+) usable (again) in products which require both OnPrem and OnDemand deploy
In many industries (e.g. medical, energy, aeronautics) companies must produce products that can also be installed in environments where no internet connectivity is available/permitted. These same products however, are also often installed in places where they can leverage cloud (OnDemand) capabilities. If IoT-Edge ist to be applicable for such products, it must (by design) provide for:
1. Installation from download or USB-stick including configuration via config file or local API (as did Edge V1)
2. Provide and abstraction layer to the external communication (as was done via Edge V1 Modules) enabling a configurable routing to use OnPremises endpoits (REST) or…64 votesHi Richard, item #3 has been addressed with the public preview of extended offline feature work. You can find out more about it at the blog post below. The rest of the issues you raise will take longer for us to add to the product.
https://azure.microsoft.com/en-us/blog/extended-offline-operation-with-azure-iot-edge/
-
Support Ubuntu Core
Add Ubuntu Core as supported Operating Systems. It is becoming a preferred "secure by default" OS which is preinstalled on many IoT Gateways. E.g. Dell Edge Gateways
56 votesWe are aware of this OS and want to get to it; however CentOS 7.5 and Yocto are currently higher on our priority list.
-
Azure blob file upload
We are planning to upgrade an existing production application from V1 to V2. In addition to streaming data (as messages to Azure IotHub), we also upload hourly aggregated data to Azure blob store. Can you share approximate time-lines when V2 can have support for Azure blob upload?
49 votes -
when processing queued messages after reconnecting, send messages with LIFO instead of FIFO as the latest data is the most important for rea
when processing queued messages after reconnecting, send messages with LIFO instead of FIFO as the latest data is the most important for real time monitoring. This is similar to the one posted already
42 votesCurrently IoT Hub and Edge Hub guarantee that messages will be delivered in order. Would folks want this promise to be broken? How would people want to rationalize ordering with other messages.
-
Store Private key for X.509 based DPS securely on HSM
Use the X.509-based enrollment in DPS in IoTEdge without storing the private key on file system.
The idea is to store the Private Key in a HSM and let it never leave.
At this moment, the x.509 provisioning mode only supports a private key on the file system...
40 votes -
C2D Messaging
I know direct methods are possible but sometimes you just want to have a queue of C2D messages which are delivered to devices when they come online. Direct methods only work when a device is connected and it would require some effort to implement the aforementioned scenario. Also one would need some routing logic to deliver those messages to modules.
37 votes -
Document how to connect Azure Sphere Device as Downstream Device to Edge
It would be great to connect the new Azure Sphere to the IoT Hub on Edge to use Sphere in a Transparent Gateway Scenario
33 votesThis is a gap that we are aware of, want to fix, and are currently discussing with the Azure Sphere team.
-
Progress bar for deployment of modules
For development, testing and monitoring purposes it would be great if there would be more information about the progress of a deployment, especially on the Edge device itself. One can look at the logfiles for the start and finish of a deployment, but I would like to know more than this. My suggestion would be to see the container in the 'iotedge list' with status downloading (42MB/100MB, 42%), but I'm open to any other form of monitoring the progress of the deployment.
27 votes -
Need a way to see a message as it is routed through the Edge
An IoT Edge message correlation id should be provided so that specific message workflows can be diagnosed via module logging.
27 votes -
(Cloud-triggered) IoT Edge Runtime Updates
Provide a way of an (automatic) cloud-triggered update mechanism for the IoT Edge Runtime through IoT Hubs Device Management. Providing update capabilities not only for the containers but for the runtime and even the underlying OS is crucial for IoT Scenarios.
26 votesDevice update for IoT Hub is now in public preview and this sample shows how to update an IoT Edge device with ADU.
-
Remote login to IoT Gateway
If an IoT Gateway is deployed in the industrial plant and if some application crashes in Gateway or some need of login to the gateway.
In that case, Azure IoT edge should allow users to remotely log in to the IoT gateway using ssh/telnet. This will very easy to monitor the status and debugging/maintenance.24 votes -
IoT Edge Module deployment limit
Currently there is a limit of 10 modules (includes agent, hub) to be deployed to IoT Edge device. What is the plan for module deployment limit for GA release? The reason is the solution we are working demands multiple (more than 8) peripheral integration at device level and we see that each Edge module could represent the peripherals. Also, please share tentative plan of GArelease?
23 votesThe limit has indeed been raised to 20. We’re interested to learn about scenarios that require more than 20 modules.
-
Certificate based Proxy Authentication
Can you please provide support for certificate based proxy authentication on IoT Edge. The certificate are client signed certificates used to securely authenticate within the client network.
19 votes -
BLE Sample
Will a BLE sample be available?
As I understand, it will require the module container to run in privileged mode to gain access to hardware devices... Is this supported?
19 votes -
Module for receiving data from BACnet systems
Alike a Modbus module, it would be useful if a BACnet module is made available to support BACnet systems.
15 votes -
sign container
Provide option during the install (only local on edge device) that forces all containers to be signed by a specific certificate.
This would allow to harden the device against a leak of the IoT Hub Management Credentials or of the Customer Platform managing the deployments.
14 votes -
Rust SDK Azure IoT Edge
Since Rust is becoming increasingly popular it would be amazing to use Rust for creating custom IoT Edge modules. Rust would be a good fit for IoT Edge modules which require high performance and safety!
14 votesThis is definitely interesting; however is unplanned at the moment. Supporting SDKs in 5 languages is already a large task and we’re not likely to add another language to that matrix anytime soon.
-
More options, or configuration parameters, of storeAndForwardConfiguration
storeAndForwardConfiguration has a parameter, timeToLiveSecs to specify offline period to retain data.
Preferable to add following 3 parameters to storeAndForwardConfiguration
1. Limit the amount of disk usage to be used for SnF feature.
2. Specify the directory/path of storage for SnF feature
3. Flush un-forwarded messages in SnF memory out to specified files12 votes
- Don't see your idea?