Azure Notification Hub Monitoring Integration
Azure Notification Hub is a scalable and easy-to-use service that enables you to send millions of push notifications with low latency to any platform.
With Site24x7's integration, you can now monitor your Azure Notification Hub, configure thresholds, and receive alerts about critical issues.
Table of contents
Setup and configuration
You can add Azure Notification Hub while adding a new monitor or you can add it to an existing Azure monitor. Follow these steps to add the service.
Supported metrics
| Metric name | Description | Statistic | Unit |
|---|---|---|---|
| Incoming Messages | The total number of successfully sent API calls | Total | Count |
| All Incoming Failed Requests | The total number of incoming failed requests | Total | Count |
| All Incoming Requests | The total number of incoming requests | Total | Count |
| Scheduled Push Notifications Sent | The total number of scheduled push notifications sent | Total | Count |
| Scheduled Push Notifications Cancelled | The total number of scheduled push notifications cancelled | Total | Count |
| Installation Management Operations | The total number of installation management operations | Total | Count |
| Delete Installation Operations | The total number of delete installation operations | Total | Count |
| Get Installation Operations | The total number of get installation operations | Total | Count |
| Patch Installation Operations | The total number of patch installation operations | Total | Count |
| Create or Update Installation Operations | The total number of create or update installation operations | Total | Count |
| All Outgoing Notifications | The total number of outgoing notifications | Total | Count |
| Bad or Expired Channel Errors | The total number of pushes that failed because either the channel token or the registration ID has expired or is invalid | Total | Count |
| Channel Errors | The total number of pushes that failed because the channel is invalid | Total | Count |
| Payload Errors | The total number of pushes that failed because the Platform Notification Systems (PNS) has returned a bad payload error | Total | Count |
| External Notification System Errors | The total number of pushes that failed because of not communicating with the PNS | Total | Count |
| Successful Notifications | The total number of successful notifications | Total | Count |
| APNS Errors | The total number of pushes that failed because of the errors in communicating with the Apple Push Notification Service (APNS) | Total | Count |
| APNS Successful Notifications | The total number of APNS successful notifications | Total | Count |
| APNS Bad Channel Error | The total number of pushes that failed because the token is invalid | Total | Count |
| APNS Expired Channel Error | The total number of tokens that were invalidated by the APNS feedback channel | Total | Count |
| APNS Authorization Errors | The total number of pushes that failed because the credentials are blocked | Total | Count |
| APNS Invalid Notification Size Error | The total number of pushes that failed because the APNS payload is too large | Total | Count |
| GCM Errors | The total number of pushes that failed because of an error in communicating with Google Cloud Messaging (GCM) | Total | Count |
| GCM Authentication Errors | The total number of pushes that failed because the PNS failed to accept the provided credentials | Total | Count |
| GCM Bad Channel Error | The total number of pushes that failed because the registration ID is not recognized | Total | Count |
| GCM Expired Channel Error | The total number of pushes that failed because the registration ID has expired | Total | Count |
| GCM Authorization Errors (Invalid Credentials) | The total number of pushes that failed because the PNS did not accept the provided credentials | Total | Count |
| GCM Invalid Notification Format | The total number of pushes that failed because the payload is not formatted correctly | Total | Count |
| GCM Invalid Notification Size Error | The total number of pushes that failed because the GCM payload is too large | Total | Count |
| GCM Successful Notifications | The total number of GCM successful notifications | Total | Count |
| GCM Throttled Notifications | The total number of pushes that failed because GCM has throttled this application | Total | Count |
| GCM Wrong Channel Error | The total number of pushes that failed because the registration ID is not associated to the current application | Total | Count |
| MPNS Authentication Errors | The total number of pushes that failed because the Microsoft Push Notification Service (MPNS) did not accept the provided credentials | Total | Count |
| MPNS Bad Channel Error | The total number of pushes that failed because the channel URI in the registration is not recognized | Total | Count |
| MPNS Channel Disconnected | The total number of pushes that failed because the channel URI in the registration was disconnected | Total | Count |
| MPNS Dropped Notifications | The total number of pushes that were dropped by MPNS | Total | Count |
| MPNS Invalid Credentials | The total number of pushes that failed because the credentials are blocked | Total | Count |
| MPNS Invalid Notification Format | The total number of pushes that failed because the MPNS payload of the notification was too large | Total | Count |
| MPNS Errors | The total number of pushes that failed because of the errors in communicating with MPNS | Total | Count |
| MPNS Successful Notifications | The total number of MPNS successful notifications | Total | Count |
| MPNS Throttled Notifications | The total number of pushes that failed because MPNS has throttled the app | Total | Count |
| WNS Authentication Errors | The total number of undelivered notifications resulting in Windows Push Notification Service (WNS) authentication errors | Total | Count |
| WNS Bad Channel Error | The total number of pushes that failed because the channel URI in the registration is not recognized | Total | Count |
| WNS Channel Disconnected | The total number of times the channel URI in the registration has throttled | Total | Count |
| WNS Channel Throttled | The total number of throttled WNS channels | Total | Count |
| WNS Dropped Notifications | The total number of dropped notifications because the channel URI in the registration has throttled | Total | Count |
| WNS Expired Channel Error | The total number of pushes that failed because the channel URI has expired | Total | Count |
| WNS Authorization Errors (Invalid Credentials) | The total number of pushes that failed because the credentials are blocked | Total | Count |
| WNS Invalid Notification Format | The total number of notification formats that are invalid | Total | Count |
| WNS Invalid Notification Size Error | The total number of WNS notification payloads that are too large | Total | Count |
| WNS Authorization Errors (Invalid Token) | The total number of WNS authorization errors | Total | Count |
| WNS Errors | The total number of notifications that are not delivered because of the errors in communicating with the WNS | Total | Count |
| WNS Successful Notifications | The total number of WNS successful notifications | Total | Count |
| WNS Throttled Notifications | The total number of pushes that failed because the WNS is throttling this application | Total | Count |
| WNS Authorization Errors (Unreachable) | The total number of errors indicating Windows Live is not reachable | Total | Count |
| WNS Authorization Errors (Wrong Token) | The total number of WNS authorization errors due to wrong tokens | Total | Count |
| Registration Operations | The total number of successful registration operations | Total | Count |
| Registration Create Operations | The total number of successful registration creations | Total | Count |
| Registration Delete Operations | The total number of successful registration deletions | Total | Count |
| Registration Read Operations | The total number of successful registration queries | Total | Count |
| Registration Update Operations | The total number of successful registration updates | Total | Count |
| Pending Scheduled Notifications | The total number of pending scheduled notifications | Total | Count |
Threshold configuration
Global configuration
- In the Site24x7 web client, go to the Admin section on the left navigation pane.
- Select Configuration Profiles from the left pane and select the Threshold and Availability (+) tab from the drop-down menu.
- Click Add Threshold Profile in the top-right corner.
- For Monitor Type, select Azure Notification Hub.
You can now set the threshold values for all the metrics listed above.
Monitor-level configuration
- In the Site24x7 web client, go to Cloud > Azure and select Azure Notification Hub from the drop-down menu.
- Choose a resource you would like to set a threshold for, then click the hamburger icon
. - Select Edit, which directs you to the Edit Azure Notification Hub Monitor page.
- You can set the threshold values for the metrics by selecting Threshold and Availability.
You can also configure IT Automation at the attribute level.
IT Automation
Site24x7 offers a set of exclusive IT Automation tools that automatically resolve performance degradation issues. These tools react to events proactively rather than waiting for manual intervention.
How to configure IT Automation for a monitor
Configuration Rules
With Site24x7's Configuration Rules, you can set parameters like Threshold Profile, Notification Profile, Tags, and Monitor Group for multiple monitors.
How to add a Configuration Rule
Related links:
How to add an Azure monitor
How to integrate an Azure App Service monitor
How to integrate Azure Virtual Machine monitor
How to configure IT Automations for a monitor
View the list of monitor reports