Azure IoT Hub Monitoring Integration
Azure IoT Hub allows you to develop IoT solutions, establish safer communication between your IoT devices, and monitor them by tracking all events.
With Site24x7's integration, you can now monitor your Azure IoT Hub, configure thresholds, and receive alerts about critical issues.
Table of contents
Setup and configuration
You can add Azure IoT Hub while adding a new monitor or you can add it to an existing Azure monitor. Follow these steps to add the service.
Supported metrics
| Metric name | Description | Statistic | Unit |
|---|---|---|---|
| C2D Messages Abandoned | The total number of cloud-to-device (C2D) messages abandoned by the device | Total | Count |
| C2D Message Deliveries Completed | The total number of C2D message deliveries completed successfully by the device | Total | Count |
| C2D Messages Rejected | The total number of C2D messages rejected by the device | Total | Count |
| Failed Direct Method Invocations | The total number of all failed direct method calls | Total | Count |
| Request Size of Direct Method Invocations | The average size of all successful direct method requests | Average | Bytes |
| Response Size of Direct Method Invocations | The average size of all successful direct method responses | Average | Bytes |
| Successful Direct Method Invocations | The number successful direct method calls | Total | Count |
| Failed Twin Reads from Back End | The number failed back-end-initiated twin reads | Total | Count |
| Response Size of Twin Reads from Back End | The average size of all successful back-end-initiated twin reads | Average | Bytes |
| Successful Twin Reads from Back End | The total number successful back-end-initiated twin reads | Total | Count |
| Failed Twin Updates from Back End | The total number of failed back-end-initiated twin updates | Total | Count |
| Size of Twin Updates from Back End | The average size of all successful back-end-initiated twin updates | Average | Bytes |
| Successful Twin Updates from Back End | The total number of successful back-end-initiated twin updates | Total | Count |
| Configuration Metrics | The total number of metrics for configuration operations | Total | Count |
| Connected Devices | The number of devices connected to your IoT hub | Average | Count |
| Routing: Messages Delivered to Messages/Events | The number of times IoT Hub routing successfully delivered messages to the built-in endpoint | Total | Count |
| Routing: Messages Delivered to Event Hub | The number of times IoT Hub routing successfully delivered messages to Event Hub endpoints | Total | Count |
| Routing: Messages Delivered to Service Bus Queue | The number of times IoT Hub routing successfully delivered messages to Service Bus queue endpoints | Total | Count |
| Routing: Messages Delivered to Service Bus Topic | The number of times IoT Hub routing successfully delivered messages to Service Bus topic endpoints | Total | Count |
| Routing: Messages Delivered to Storage | The number of times IoT Hub routing successfully delivered messages to storage endpoints | Total | Count |
| Routing: Blobs Delivered to Storage | The number of times IoT Hub routing delivered blobs to storage endpoints | Total | Count |
| Routing: Data Delivered to Storage | The amount of data IoT Hub routing delivered to storage endpoints | Total | Bytes |
| Routing: Message Latency for Messages/Events | The average latency between message ingress to IoT Hub and telemetry message ingress into the built-in endpoint | Average | Milliseconds |
| Routing: Message Latency for Event Hub | The average latency between message ingress to IoT Hub and message ingress into an Event Hub endpoint | Average | Milliseconds |
| Routing: Message Latency for Service Bus Queue | The average latency between message ingress to IoT Hub and telemetry message ingress into a Service Bus queue endpoint | Average | Milliseconds |
| Routing: Message Latency for Service Bus Topic | The average latency between message ingress to IoT Hub and telemetry message ingress into a Service Bus topic endpoint | Average | Milliseconds |
| Routing: Message Latency for Storage | The average latency between message ingress to IoT Hub and telemetry message ingress into a storage endpoint | Average | Milliseconds |
| Routing: Telemetry Messages Dropped | The number of times messages were dropped by IoT Hub routing due to dead endpoints | Total | Count |
| Routing: Messages Delivered to Fallback | The number of times IoT Hub routing delivered messages to the endpoint associated with the fallback route | Total | Count |
| Routing: Telemetry Messages Incompatible | The number of times IoT Hub routing failed to deliver messages due to an incompatibility with the endpoint | Total | Count |
| Routing: Telemetry Messages Orphaned | The number of times messages were orphaned by IoT Hub routing because they didn't match any routing rules | Total | Count |
| Routing: Telemetry Messages Delivered | The number of times messages were successfully delivered to all endpoints using IoT Hub routing | Total | Count |
| Telemetry Message Send Attempts | The number of device-to-cloud telemetry messages attempted to be sent to your IoT hub | Total | Count |
| Number of Throttling Errors | The total number of throttling errors due to device throughput throttles | Total | Count |
| Telemetry Messages Sent | The total number of device-to-cloud telemetry messages sent successfully to your IoT hub | Total | Count |
| Failed Twin Reads from Devices | The number of all failed device-initiated twin reads | Total | Count |
| Response Size of Twin Reads from Devices | The average amount of data of all successful device-initiated twin reads | Average | Bytes |
| Successful Twin Reads from Devices | The total number of all successful device-initiated twin reads | Total | Count |
| Failed Twin Updates from Devices | The total number of all failed device-initiated twin updates | Total | Count |
| Size of Twin Updates from Devices | The average size of all successful device-initiated twin updates | Average | Bytes |
| Successful Twin Updates from Devices | The number of all successful device-initiated twin updates | Total | Count |
| Total Number of Messages Used | The number of total messages used today | Maximum | Count |
| Total Device Data Usage | The amount of data transferred to and from any devices connected to your IoT hub | Total | Bytes |
| Total Device Data Usage (preview) | The amount of data transferred to and from any devices connected to your IoT hub (preview) | Total | Bytes |
| Connected Devices (deprecated) | The number of devices connected to your IoT hub | Total | Count |
| Total Devices (deprecated) | The number of devices registered | Total | Count |
| Failed Job Cancellations | The total number of all failed calls to cancel a job | Total | Count |
| Successful Job Cancellations | The total number of all successful calls to cancel a job | Total | Count |
| Completed Jobs | The total number of all completed jobs | Total | Count |
| Failed Creations of Method Invocation Jobs | The total number of all unsuccessfully created direct method invocation jobs | Total | Count |
| Successful Creations of Method Invocation Jobs | The total number of all successfully created direct method invocation jobs | Total | Count |
| Failed Creations of Twin Update Jobs | The number of all unsuccessfully created twin update jobs | Total | Count |
| Successful Creations of Twin Update Jobs | The number of all successfully created twin update jobs | Total | Count |
| Failed Jobs | The number of all failed jobs | Total | Count |
| Failed Calls to List Jobs | The number of all failed calls to list jobs | Total | Count |
| Successful Calls to List Jobs | The number of all successful calls to list jobs | Total | Count |
| Failed Job Queries | The number of all failed calls to query jobs | Total | Count |
| Successful Job Queries | The number of all successful calls to query jobs | Total | Count |
| Total Devices | The number of devices registered to your IoT hub | Average | Count |
| Failed Twin Queries | The number of all failed twin queries | Total | Count |
| Twin Queries Result Size | The average result size of all successful twin queries | Average | Bytes |
| Successful Twin Queries | The number of all successful twin queries | Total | Count |
Threshold configuration
Global configuration
- In the Site24x7 web client, go to the Admin section on the left navigation pane.
- Select Configuration Profiles from the left pane and select the Threshold and Availability (+) tab from the drop-down menu.
- Click Add Threshold Profile in the top-right corner.
- For Monitor Type, select Azure IoT Hub.
You can now set the threshold values for all the metrics listed above.
Monitor-level configuration
- In the Site24x7 web client, go to Cloud > Azure and select Azure IoT Hub from the drop-down menu.
- Choose a resource you would like to set a threshold for, then click the hamburger icon
. - Select Edit, which directs you to the Edit Azure IoT Hub Monitor page.
- You can set the threshold values for the metrics by selecting Threshold and Availability.
You can also configure IT Automation at the attribute level.
IT Automation
Site24x7 offers a set of exclusive IT Automation tools that automatically resolve performance degradation issues. These tools react to events proactively rather than waiting for manual intervention.
How to configure IT Automation for a monitor
Configuration Rules
With Site24x7's Configuration Rules, you can set parameters like Threshold Profile, Notification Profile, Tags, and Monitor Group for multiple monitors.
How to add a Configuration Rule
Related links:
How to add an Azure monitor
How to integrate an Azure App Service monitor
How to integrate Azure Virtual Machine monitor
How to configure IT Automations for a monitor
View the list of monitor reports