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.
-
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.
17 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
16 votesThis is a gap that we are aware of, want to fix, and are currently discussing with the Azure Sphere team.
-
Hierarchy possibilities for edge devices.
The purpose is to have for example 5 incoming sensors in the 'sensor' edge device where we can do some calculations on the edge. The output goes to another edge device, where again we can do some calculations on the edge with input from other similar 'sensor' edge devices. The last edge device in the chain will send the data to the IoT Hub.
10 votesThis is definitely a scenario we want to support in the future.
-
Need a way to distribute communication at edge devices when offline with IoT hub
During offline with IoT hub, is it possible to have a mechanism at Edge device to distribute the messages among other Edge devices? This will help to address a scenario were one Edge device needs to share message/information with another Edge device as there is no cloud data storage share available due to
connectivity issue.8 votes -
Leaf to Leaf communitation through Edge
Is leaf to leaf communication through Edge (routing) with and without internet connectivity in the roadmap?
2 votes -
Log a Warning if messages are deleted from the StoreAndForward/offline cache (because of TTL)
Currently there is no way to figure out that messages were deleted because of the Time To Live/TTL StoreAndForward configuration. There should be a warning in the Logs if this happens to hint the deletion of messages that were not sent to IoT Hub. Ideally there is a configurable second warning before this happens (e.g. 10 minutes before messages get deleted because of TTL).
In addition it would be great to add more control to the StoreAndForward/Caching/Queuing functionality of messaging - refer to ideas https://feedback.azure.com/forums/907045-azure-iot-edge/suggestions/33534802-more-options-or-configuration-parameters-of-stor and https://feedback.azure.com/forums/907045-azure-iot-edge/suggestions/36632884-low-bandwidth-partially-connected-message-deliv2 votes -
Low bandwidth / partially connected: message delivery priority
For scenarios with low bandwidth and connectivity issues sending messages in the FIFO order of the message cache after being offline is not working. We need a way to specify "important" messages (delivery priority) that needs to be sent before trying to send all other messages from the msg cache. Specifying different TTL values for different priorities would be necessary as well.
2 votes -
Local Edge N+M high availability and scalability (no cloud connection required after setup)
1) Deploy Edges as local clusters such that they can suffer failure and there is a high availability strategy that doesn't require a cloud connection.
2) Edge scalability to horizontally add nodes to the Local Edge Cluster. Maybe it kind of behaves like Docker Swarm. i.e. Say I have a pretty intense preprocessor for data prep before handing it to ML Inference. That could get scaled out across multiple nodes in a Local Edge Cluster.
2 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
1 vote -
Stop Module Only After Container Download Completes Successfully
I have noticed that when you deploy an update to a module, edgeAgent stops the module to update, downloads the new image, and then runs the new image of the module. This works fine when the connection is good and/or the image is small. When the connection is poor and/or the image is large, however, it may take a while to update which means the module is down for a while.
To increase availability, particularly with bad connections/big images, why doesn't edgeAgent only stop the old module once the new one has finished updating? I've had experiences where a module…
1 vote -
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.
1 vote
- Don't see your idea?