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.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. 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.

    6 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    started  ·  1 comment  ·  Connectivity issues  ·  Flag idea as inappropriate…  ·  Admin →
  2. 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-deliv

    3 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Connectivity issues  ·  Flag idea as inappropriate…  ·  Admin →

    We are currently adding the ability to pull metrics from the runtime so that customers can understand how their Edge devices are performing in the field. Message drops due to TTL is one of the metrics we’ll be exposing. I do not expect this feature for a few months, likely 1.0.10.

  3. 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.

    3 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Connectivity issues  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base