Azure Notification Hubs provide an easy-to-use and scaled-out push engine that enables you to send notifications to any platform (iOS, Android, Windows, etc.) from any back-end (cloud or on-premises). This integration helps in monitoring the operations and actions that are conducted against your Azure Notification Hubs namespace.
Log and Metric types
For Azure Notification Hubs, you can collect the following logs:
- Diagnostic Logs. These logs are from operations and actions that are conducted against your namespace by using the API, or through management clients on the language SDK.
For more details on logs collected, refer to the logs schema documentation.
Azure service sends monitoring data to Azure Monitor, which can then stream data to Eventhub. Sumo Logic supports:
You must explicitly enable diagnostic settings for each Azure Notification Hubs namespace 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 or HTTP source, plan your source category to ease the querying process. A hierarchical approach allows you to make use of wildcards. For example:
Configure logs collection
In this section, you will configure a pipeline for shipping diagnostic logs from Azure Monitor to an Event Hub.
- To set up the Azure Event Hubs cloud-to-cloud source in Sumo Logic portal, refer to our Azure Event Hubs source documentation.
- To create the Diagnostic settings in Azure portal, refer to the Azure documentation. Perform below steps for each Azure Notification Hubs namespace that you want to monitor.
Stream to an event hubas the destination.
- Use the Event hub namespace and Event hub name configured in previous step in destination details section. You can use the default policy
RootManageSharedAccessKeyas the policy name.
Azure Event Hubs Source
Common error types are described here.
You can try restarting the source for