Microsoft Azure IOT Hub
This SAM application monitor template contains metrics, including ingress and egress telemetry, for monitoring Microsoft Azure IOT Hub. Some counters may require manual configuration, such as setting up installation-specific instances or correcting thresholds for your environment.
Passwords for legacy Microsoft Azure application monitor templates and related application monitors are stored as plain text in the SolarWinds Platform database. SolarWinds recommends switching to Microsoft Azure API poller templates that leverage OAuth 2.0 authorization.”
Prerequisites
-
PowerShell modules (Az, Az.Accounts, Az.Resources) installed
-
Parameters for connecting to your Azure account
-
Subscription ID
-
Application ID
-
Tenant ID
-
Secret Key
-
-
Any Azure App (with its name and ID) having minimum role as Read Only
-
IOT Hub name for which metrics are being calculated
- PowerShell 5.1 or later
Credentials
- Windows Administrator privileges on the target system
- Login credential to access the Azure Portal, passed as script arguments per prerequisites (<SubscriptionID>, <TenantID>, <ApplicationID>, value=<Secret Key>, <Namespace Name>, Resource Group Name, value=<Time Interval>)
- Optional parameters can be passed to script argument:
- Time interval for which data has to be fetched (in hours).
- Number of retries as the second last argument; the default is 3 seconds.
- WaitTime as the last argument; the default is 0.5 seconds.
Notes
- Run scripts as the Administrator.
- The ApplicationID used to connect to the Azure portal must be registered in Azure Active Directory with a read-only/contributor role for the monitored application. See Add an Azure Active Directory app for cloud monitoring in the SolarWinds Platform.
- Portions of this document are excerpts from the following sources:
Component monitors
Commands abandoned
The total count of Cloud to Device commands abandoned by the device via PowerShell cmd-let.
Unit: Count
Commands completed
The total count of Cloud to Device commands successfully by the device via PowerShell cmd-let.
Unit: Count
Commands rejected
The total count of Cloud to Device commands successfully by the device via PowerShell cmd-let.
Unit: Count
Failed direct method invocations
The total count of failed Cloud to Device method invocations by the device via PowerShell cmd-let.
Unit: Count
Request size of direct method invocations
The Average Request size of Cloud to Device method invocations via PowerShell cmd-let.
Unit: Bytes
Response size of direct method invocations
The Average Response size of Cloud to Device method invocations via PowerShell cmd-let.
Unit: Bytes
Successful direct method invocations
The total count of successful Cloud to Device method invocations by the device via PowerShell cmd-let.
Unit: Count
Failed twin reads from back end
The total count of failed backend-initiated twin reads.
Unit: Count
Response size of twin reads from back end
The average Response size of backend-initiated twin reads.
Unit: Bytes
Successful twin reads from back end
The total count of successful backend-initiated twin reads.
Unit: Count
Failed twin updates from devices
The total count of failed device-initiated twin updates.
Unit: Count
Size of twin updates from devices
The average Response size of device-initiated twin updates.
Unit: Bytes
Successful twin updates from devices
The total count of successful device-initiated twin updates.
Unit: Count
Messages delivered to the built-in endpoint
The total count of messages successfully written to the built-in endpoint.
Unit: Count
Messages delivered to Event Hub endpoints
The total count of messages successfully written to the Event Hub endpoints.
Unit: Count
Messages delivered to Service Bus Queue endpoints
The total count of messages successfully written to the Service Bus Queues endpoints.
Unit: Count
Messages delivered to Service Bus Topic endpoints
The total count of messages successfully written to the Service Bus Topics endpoints.
Unit: Count
Message latency for the built-in endpoint
The average latency between message ingress to the IoT hub and message ingress into the built-in endpoint.
Unit: Milliseconds
Message latency for Event Hub endpoints
The average latency between message ingress to the IoT hub and message ingress into the Event Hub endpoint.
Unit: Milliseconds
Message latency for Service Bus Queue endpoints
The average latency between message ingress to the IoT hub and message ingress into a Service Bus Queue endpoint.
Unit: Milliseconds
Message latency for Service Bus Topic endpoints
The average latency between message ingress to the IoT hub and message ingress into a Service Bus Topic endpoint.
Unit: Milliseconds
Dropped messages
The total count of messages dropped because they did not match any routes and the fallback route was disabled.
Unit: Count
Messages matching fallback condition
The total count of messages written to the fallback endpoint.
Unit: Count
Invalid messages
The total count of messages not delivered due to incompatibility with the endpoint.
Unit: Count
Orphaned messages
The total count of messages not matching any routes including the fallback route.
Unit: Count
Telemetry messages delivered
The count of times messages were successfully written to endpoints.
Unit: Count
Telemetry message send attempts
The total count of Device to Cloud telemetry messages attempted to be sent to IOT Hub.
Unit: Count
Telemetry messages sent
The total count of Device to Cloud telemetry messages successfully sent to IOT Hub.
Unit: Count
Failed twin reads from devices
The total count of failed device-initiated twin reads.
Unit: Count
Response size of twin reads from devices
This monitor provides the average Response size of device-initiated twin reads.
Unit: Bytes
Successful twin reads from devices
The total count of successful device-initiated twin reads.
Unit: Count
Failed twin updates from devices
The total count of failed device-initiated twin updates.
Unit: Count
Size of twin updates from devices
The average response size of device-initiated twin updates.
Unit: Bytes
Successful twin updates from devices
The total count of successful device-initiated twin updates.
Unit: Count
Connected devices
The total count of devices connected to your IoT hub.
Unit: Count
Total devices
The total count of devices registered to your IoT hub.
Unit: Count
Failed job cancellations
The count of failed calls to cancel a job.
Unit: Count
Successful job cancellations
The total count of successful calls to cancel a job.
Unit: Count
Completed jobs
The total count of completed jobs.
Unit: Count
Failed creations of method invocation jobs
The total count of failed creations of direct method invocation jobs.
Unit: Count
Successful creations of method invocation jobs
The total count of successful creations of direct method invocation jobs.
Unit: Count
Failed creations of twin update jobs
This monitor provides the total count of failed creations of twin update jobs.
Unit: Count
Successful creations of twin update jobs
The total count of successful creations of twin update jobs.
Unit: Count
Failed jobs
The total count of failed jobs.
Unit: Count
Failed calls to list jobs
The total count of failed calls to list jobs.
Unit: Count
Successful calls to list jobs
This monitor provides the total count of successful calls to list jobs.
Unit: Count
Failed job queries
This monitor provides the total count of failed calls to query jobs.
Unit: Count
Successful job queries
The total count of successful calls to query jobs.
Unit: Count
Failed twin queries
The total count of failed twin queries.
Unit: Count
Twin queries result size
The average result size of successful twin queries.
Unit: Bytes
Successful twin queries
The total count of successful twin queries.
Unit: Count