New Relic's integrations include an integration for reporting your Microsoft Azure Notification Hubs 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 Notification Hubs service. 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). Notification Hubs work great for both enterprise and consumer scenarios.
Using New Relic, you can:
- View Azure Notification Hubs 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 standard Azure 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 Notification Hubs service through 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 Notification Hubs metrics
Metric | Description |
|---|---|
| The count of all successful send API calls.. |
| Total incoming failed requests for a notification hub. |
| Total incoming requests for a notification hub. |
| Scheduled push notifications sent. |
| Scheduled push notifications cancelled. |
| Installation management Operations. |
| Delete installation operations. |
| Get installation operations. |
| Patch installation operations. |
| Create or Update installation operations. |
| All outgoing notifications of the notification hub. |
| The count of pushes that failed because the channel/token/registrationId in the registration was expired or invalid. |
| The count of pushes that failed because the channel was invalid not associated with the correct app throttled or expired.. |
| The count of pushes that failed because the PNS returned a bad payload error. |
| The count of pushes that failed because there was a problem communicating with the PNS (excludes authentication problems). |
| The count of all successful notifications. |
| The count of pushes that failed because the token is invalid (APNS status code: 8). |
| The count of token that were invalidated by the APNS feedback channel. |
| The count of pushes that failed because the PNS did not accept the provided credentials or the credentials are blocked. |
| The count of pushes that failed because the payload was too large (APNS status code: 7). |
| The count of pushes that failed because of errors communicating with APNS. |
| The count of all successful notifications. |
| The count of pushes that failed because the PNS did not accept the provided credentials the credentials are blocked or the SenderId is not correctly configured in the app (GCM result: MismatchedSenderId). |
| The count of pushes that failed because the registrationId in the registration was not recognized (GCM result: Invalid Registration). |
| The count of pushes that failed because the registrationId in the registration was expired (GCM result: NotRegistered). |
| The count of pushes that failed because the PNS did not accept the provided credentials or the credentials are blocked. |
| The count of pushes that failed because the payload was not formatted correctly (GCM result: InvalidDataKey or InvalidTtl). |
| The count of pushes that failed because the payload was too large (GCM result: MessageTooBig). |
| The count of pushes that failed because of errors communicating with GCM. |
| The count of all successful notifications. |
| The count of pushes that failed because GCM throttled this app (GCM status code: 501-599 or result:Unavailable). |
| The count of pushes that failed because the registrationId in the registration is not associated to the current app (GCM result: InvalidPackageName). |
| The count of pushes that failed because the PNS did not accept the provided credentials or the credentials are blocked. |
| The count of pushes that failed because the ChannelURI in the registration was not recognized (MPNS status: 404 not found). |
| The count of pushes that failed because the ChannelURI in the registration was disconnected (MPNS status: 412 not found). |
| The count of pushes that were dropped by MPNS (MPNS response header: X-NotificationStatus: QueueFull or Suppressed). |
| The count of pushes that failed because the PNS did not accept the provided credentials or the credentials are blocked. |
| The count of pushes that failed because the payload of the notification was too large. |
| The count of pushes that failed because of errors communicating with MPNS. |
| The count of all successful notifications. |
| The count of pushes that failed because MPNS is throttling this app (WNS MPNS: 406 Not Acceptable). |
| Notification not delivered because of errors communicating with Windows Live invalid credentials or wrong token. |
| The count of pushes that failed because the ChannelURI in the registration was not recognized (WNS status: 404 not found). |
| The notification was dropped because the ChannelURI in the registration is throttled (WNS response header: X-WNS-DeviceConnectionStatus: disconnected). |
| The notification was dropped because the ChannelURI in the registration is throttled (WNS response header: X-WNS-NotificationStatus:channelThrottled). |
| The notification was dropped because the ChannelURI in the registration is throttled (X-WNS-NotificationStatus: dropped but not X-WNS-DeviceConnectionStatus: disconnected). |
| The count of pushes that failed because the ChannelURI is expired (WNS status: 410 Gone). |
| The count of pushes that failed because the PNS did not accept the provided credentials or the credentials are blocked. (Windows Live does not recognize the credentials). |
| The format of the notification is invalid (WNS status: 400). Note that WNS does not reject all invalid payloads. |
| The notification payload is too large (WNS status: 413). |
| The token provided to WNS is not valid (WNS status: 401 Unauthorized). |
| Notification not delivered because of errors communicating with WNS. |
| The count of all successful notifications. |
| The count of pushes that failed because WNS is throttling this app (WNS status: 406 Not Acceptable). |
| Windows Live is not reachable. |
| The token provided to WNS is valid but for another application (WNS status: 403 Forbidden). This can happen if the ChannelURI in the registration is associated with another app. Check that the client app is associated with the same app whose credentials are in the notification hub. |
| The count of all successful registration operations (creations updates queries and deletions). |
| The count of all successful registration creations. |
| The count of all successful registration deletions. |
| The count of all successful registration queries. |
| The count of all successful registration updates. |
| Pending Scheduled Notifications |