New Relic's integrations include an integration for reporting your Microsoft Azure IoT Hub metrics and other data to New Relic. This document explains how to activate the integration and describes the data reported.
Features
New Relic gathers metrics data from Azure Monitor for the Azure IoT Hub service. Azure IoT Hub is a managed service hosted in the cloud that acts as a central message hub for communication between an IoT application and its attached devices. Using New Relic, you can:
- View Azure IoT Hub data in pre-built dashboards.
- Run custom queries and visualize the data.
- Create alert conditions to notify you of changes in data.
Activate integration
Follow standardAzure Monitor integration procedure to activate your Azure service in New Relic infrastructure monitoring.
Configuration and polling
You can change the polling frequency and filter data using configuration options.
New Relic queries your Azure IoT Hub services through the Azure Monitor integration according to a default polling interval.
Find and use data
To explore your integration data, go to one.newrelic.com/infra > Azure > (select an integration).
Metric data
This integration collects the following metric data:
Azure IoT Hub metrics
Metric | Description |
|---|---|
| Number of cloud-to-device messages abandoned by the device. |
| Number of cloud-to-device message deliveries completed successfully by the device. |
| Number of cloud-to-device messages rejected by the device. |
| The count of all failed direct method calls. |
| The average, min, and max of all successful direct method requests. |
| The average, min, and max of all successful direct method responses. |
| The count of all successful direct method calls. |
| The count of all failed back-end-initiated twin reads. |
| The count of all successful back-end-initiated twin reads. |
| The average, min, and max of all successful back-end-initiated twin reads. |
| The count of all failed back-end-initiated twin updates. |
| The average, min, and max size of all successful back-end-initiated twin updates. |
| The count of all successful back-end-initiated twin updates. |
| Number of expired cloud-to-device messages. |
| Metrics for Configuration operations. |
| Number of devices connected to your IoT hub. |
| The number of times IoT Hub routing successfully delivered messages to the built-in endpoint (messages/events). |
| The number of times IoT Hub routing successfully delivered messages to Event Hub endpoints. |
| The number of times IoT Hub routing successfully delivered messages to Service Bus queue endpoints. |
| The number of times IoT Hub routing successfully delivered messages to Service Bus topic endpoints. |
| The number of times IoT Hub routing successfully delivered messages to storage endpoints. |
| The number of times IoT Hub routing delivered blobs to storage endpoints. |
| The amount of data (bytes) IoT Hub routing delivered to storage endpoints. |
| The average latency (milliseconds) between message ingress to IoT Hub and telemetry message ingress into the built-in endpoint (messages/events). |
| The average latency (milliseconds) between message ingress to IoT Hub and message ingress into an Event Hub endpoint. |
| The average latency (milliseconds) between message ingress to IoT Hub and telemetry message ingress into a Service Bus queue endpoint. |
| The average latency (milliseconds) between message ingress to IoT Hub and telemetry message ingress into a Service Bus topic endpoint. |
| The average latency (milliseconds) between message ingress to IoT Hub and telemetry message ingress into a storage endpoint. |
| The number of times messages were dropped by IoT Hub routing due to dead endpoints. This value does not count messages delivered to fallback route as dropped messages are not delivered there. |
| The number of times IoT Hub routing delivered messages to the endpoint associated with the fallback route. |
| The number of times IoT Hub routing failed to deliver messages due to an incompatibility with the endpoint. This value does not include retries. |
| The number of times messages were orphaned by IoT Hub routing because they didn't match any routing rules (including the fallback rule). |
| The number of times messages were successfully delivered to all endpoints using IoT Hub routing. If a message is routed to multiple endpoints, this value increases by one for each successful delivery. If a message is delivered to the same endpoint multiple times, this value increases by one for each successful delivery. |
| Number of device-to-cloud telemetry messages attempted to be sent to your IoT hub. |
| Number of throttling errors due to device throughput throttles. |
| Number of device-to-cloud telemetry messages sent successfully to your IoT hub. |
| The count of all failed device-initiated twin reads. |
| The average, min, and max of all successful device-initiated twin reads. |
| The count of all successful device-initiated twin reads. |
| The count of all failed device-initiated twin updates. |
| The average, min, and max size of all successful device-initiated twin updates. |
| The count of all successful device-initiated twin updates. |
| Number of total messages used today. |
| Bytes transferred to and from any devices connected to IotHub. |
| Bytes transferred to and from any devices connected to IotHub. |
| Number of devices connected to your IoT hub. |
| Number of devices registered to your IoT hub. |
| The number of IoT Hub events published to Event Grid. Use the Result dimension for the number of successful and failed requests. EventType dimension shows the type of event. |
| The average latency (milliseconds) from when the IoT Hub event was generated to when the event was published to Event Grid. This number is an average between all event types. Use the EventType dimension to see latency of a specific type of event. |
| The count of all failed calls to cancel a job. |
| The count of all successful calls to cancel a job. |
| The count of all completed jobs. |
| The count of all failed creation of direct method invocation jobs. |
| The count of all successful creation of direct method invocation jobs. |
| The count of all failed creation of twin update jobs. |
| The count of all successful creation of twin update jobs. |
| The count of all failed jobs. |
| The count of all failed calls to list jobs. |
| The count of all successful calls to list jobs. |
| Failed job queries. |
| The count of all successful calls to query jobs. |
| The total size in bytes of messages delivered by IoT hub to an endpoint. You can use the EndpointName and EndpointType dimensions to view the size of the messages in bytes delivered to your different endpoints. The metric value increases for every message delivered, including if the message is delivered to multiple endpoints or if the message is delivered to the same endpoint multiple times. |
| The number of times IoT Hub attempted to deliver messages to all endpoints using routing. To see the number of successful or failed attempts, use the Result dimension. To see the reason of failure, like invalid, dropped, or orphaned, use the FailureReasonCategory dimension. You can also use the EndpointName and EndpointType dimensions to understand how many messages were delivered to your different endpoints. The metric value increases by one for each delivery attempt, including if the message is delivered to multiple endpoints or if the message is delivered to the same endpoint multiple times. |
| The average latency (milliseconds) between message ingress to IoT Hub and telemetry message ingress into an endpoint. You can use the EndpointName and EndpointType dimensions to understand the latency to your different endpoints. |
| Number of devices registered to your IoT hub. |
| The count of all failed twin queries. |
| The average, min, and max of the result size of all successful twin queries. |
| The count of all successful twin queries. |