Search results
Mar 15, 2023 · IoT Hub was developed to address the unique requirements of connecting IoT devices to the Azure cloud while Event Hubs was designed for big data streaming. Microsoft recommends using Azure IoT Hub to connect IoT devices to Azure. Azure IoT Hub is the cloud gateway that connects IoT devices to gather data and drive business insights and ...
- Overview
- Regional availability
- Event types
- Event schema
- Filter events
- Limitations for device connection state events
- Tips for consuming events
- Next steps
Azure IoT Hub integrates with Azure Event Grid so that you can send event notifications to other services and trigger downstream processes. Configure your business applications to listen for IoT Hub events so that you can react to critical events in a reliable, scalable, and secure manner. For example, build an application that updates a database, creates a work ticket, and delivers an email notification every time a new IoT device is registered to your IoT hub.
Azure Event Grid is a fully managed event routing service that uses a publish-subscribe model. Event Grid has built-in support for Azure services like Azure Functions and Azure Logic Apps, and can deliver event alerts to non-Azure services using webhooks. For a complete list of the event handlers that Event Grid supports, see An introduction to Azure Event Grid.
The Event Grid integration is available for IoT hubs located in the regions where Event Grid is supported. For the latest list of regions, see Products available by region.
IoT Hub publishes the following event types:
Use either the Azure portal or Azure CLI to configure which events to publish from each IoT hub. For an example, try the tutorial Send email notifications about Azure IoT Hub events using Logic Apps.
IoT Hub events contain all the information you need to respond to changes in your device lifecycle. You can identify an IoT Hub event by checking that the eventType property starts with Microsoft.Devices. For more information about how to use Event Grid event properties, see the Event Grid event schema.
Event Grid enables filtering on event types, subjects, and data content. While creating the Event Grid subscription, you can choose to subscribe to selected IoT events.
•Event type: For the list of IoT Hub event types, see event types.
•Subject: For IoT Hub events, the subject is the device name. The subject takes the format devices/{deviceId}. You can filter subjects based on Begins With (prefix) and Ends With (suffix) matches. The filter uses an AND operator, so events with a subject that match both the prefix and suffix are delivered to the subscriber.
•Data content: The data content is populated by IoT Hub using the message format. You can choose what events are delivered based on the contents of the telemetry message. For examples, see advanced filtering. For filtering on the telemetry message body, you must set the contentType to application/json and contentEncoding to UTF-8 in the message system properties. Both of these properties are case insensitive.
Device connected and device disconnected events are available for devices connecting using either the MQTT or AMQP protocol, or using either of these protocols over WebSockets. Requests made only with HTTPS won't trigger device connection state notifications.
For information about monitoring device status with Event Grid, see Monitor device connection status.
Applications that handle IoT Hub events should follow these suggested practices:
•Multiple subscriptions can be configured to route events to the same event handler, so don't assume that events are from a particular source. Always check the message topic to ensure that it comes from the IoT hub that you expect.
•Don't assume that all events you receive are the types that you expect. Always check the eventType before processing the message.
•Messages can arrive out of order or after a delay. Use the etag field to understand if your information about objects is up to date for device created or device-deleted events.
•Learn how to order device connected and disconnected events
•Compare the differences between routing IoT Hub events and messages
People also ask
What is Azure IoT Hub?
How do I publish IoT Hub events?
What is the difference between IoT Hub and event hub?
How do I publish events from Azure IoT Hubs?
Jan 14, 2024 · An IoT hub exposes the following properties to enable you to control the built-in Event Hub-compatible messaging endpoint messages/events. Set this property at creation to define the number of partitions for device-to-cloud event ingestion. This property specifies how long in days messages are retained by IoT Hub.
Apr 15, 2024 · Azure Event Hubs is a powerful tool for organizations needing to ingest, store, and process large volumes of data in real-time. Its scalability, reliability, and integration capabilities make it ...
22 hours ago · Configure event subscriptions on namespace topics to send messages to Azure Event Hubs. Since Event Hubs is compatible with Apache Kafka, this means customers can now run existing Kafka workloads without any code changes.
Jun 8, 2023 · Azure IoT Hub is a fully managed service that helps enable reliable and secure bi-directional communications between millions of devices and a solution back end. Note. Some of the features mentioned in this article, like cloud-to-device messaging, device twins, and device management, are only available in the standard tier of IoT Hub. For more ...
Learn about Azure IoT SDKs. Use the Azure IoT Hub extension for VS Code. Supported device protocols. Learn how to use Azure IoT Hub to connect, monitor, and control billions of Internet of Things assets.
