Azure IoT Hub

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. This integration helps in monitoring the device creation, device connections, device operations, device data usage, and device failures.

Log and metric types

For Azure IoT Hub, you can collect the following logs and metrics:

• Resource logs. To learn more about the different resource log category types and schemas collected for Azure IoT Hub, refer to the Azure documentation.
• Platform Metrics for Azure IoT Hub. These metrics are available in Microsoft.Devices/IotHubs namespace. For more information on supported metrics, refer to the Azure documentation.

Setup

Configure collector

Create a hosted collector if not already configured. Make sure you create the required sources in this collector.

Configure logs collection

Azure service sends monitoring data to Azure Monitor, which can then stream data to Eventhub. Sumo Logic supports collecting logs from Azure Monitor using our Azure Event Hubs source.

You must explicitly enable diagnostic settings for each Azure IoT Hub you want to monitor. You can forward logs to the same event hub provided they satisfy the limitations and permissions as described here.

When you configure the event hubs source, plan your source category to ease the querying process. A hierarchical approach allows you to make use of wildcards. For example: Azure/IoTHub/Logs.

In this section, you will configure a pipeline for shipping diagnostic logs from Azure Monitor to an Event Hub.

1. To set up the Azure Event Hubs source in Sumo Logic, refer to Azure Event Hubs Source for Logs.
2. To create the Diagnostic settings in the Azure portal, refer to the Azure documentation. Perform the steps below for each Azure IoT Hub that you want to monitor.
   • Choose Stream to an event hub as the destination.
   • Select allLogs.
   • Use the Event hub namespace and Event hub name configured in the previous step in the destination details section. You can use the default policy RootManageSharedAccessKey as the policy name.

Configure metrics collection

When you configure the Azure Metrics Source, plan your source category to ease the querying process. A hierarchical approach allows you to make use of wildcards. For example: Azure/IoTHub/Metrics.

To set up the Azure Metrics source in Sumo Logic, refer to Azure Metrics Source.

Troubleshooting

Metrics collection via Azure Metrics Source

To troubleshoot metrics collection via Azure Metrics Source, follow the instructions in Troubleshooting Azure Metrics Source.