Monitoring Azure Service Bus Topics and Subscriptions
The Nodinite Monitoring features for Azure Service Bus Topics makes sure you get alerts whenever there is a problem like performance, stockpiling messages and also provides you with remote actions to resolve issues with dead letter messages and more.
This section describes what's being monitored and the rules for how Nodinite translates this into meaningful monitoring. Also, some remote commands are available as Actions to help you swiftly manage problems. These Remote Actions are further detailed on the Managing Azure Service Bus Topic page.
From the set of named Resource Groups; The agent auto-discovers deployed Azure Service Bus Topics and Subscriptions. These are presented as Resources in the Nodinite Monitor Views.
Here's an example of Nodinite Monitoring of Azure Service Bus Topics.
Monitoring Features
- No coding required(!)
- Automatic Discovery
- Nodinite Azure agents use the SDK and the Azure Rest API and offer you an automatic discovery of your Azure Service Bus Topics. Sharing access to any individual Topic and Subscription is very easy from within Nodinite.
- State Evaluation - Make sure the Azure Service Bus resources have the intended run-time state and not stockpiling messages
If Nodinite can't check the state of your Azure Service Bus resources, chances are no one else can either.
The following Azure Service Bus Resources are monitored by using this agent, grouped by the Nodinite Category feature:
- Service Bus Queues
- Service Bus Topics
- Operational monitoring
- Subscription (make sure the topic is operational)
- Dead-letter detection
- Age verification
- Count (warning/error)
- Resource groups
- Service Bus Configuration
State evaluation
Each monitored 'Service Bus Topic', and 'Service Bus Topic Subscription' is displayed in Nodinite Monitor Views as Resources with its currently evaluated state. If you have 11 deployed Azure Service Bus Topics with only 1 subscription each, then you will have 22 Resources in Nodinite with potentially different monitored evaluated states at any given moment.
Live overview with different states summarized in a pie chart
The evaluated state may be reconfigured using the Expected State override setting on every Resource within Nodinite.
Azure Service Bus Topic
All Azure Service Bus Topics belong to the 'Service Bus Topic' category:
The Application name is based on physical deployment paths. This pattern guarantees uniqueness:
- subscription name/resource group name/namespace name
Here's an example of Application naming pattern providing uniqueness
Each monitored Service Bus Topic is a Resource and can have one of the following states at any given moment:
| State | Status | Description | Actions | |
|---|---|---|---|---|
| Unavailable | Resource not available |
|
Review prerequisites | |
| Error | Error threshold is breached |
|
Edit thresholds Details Enable Disable | |
| Warning | Warning threshold is breached | Not yet implemented | ||
| OK | Within user-defined thresholds | Topic is operational | Edit thresholds Details Enable Disable |
Azure Service Bus
For each 'Service Bus' configuration; The Service Bus Category lists each unique namespace as a Resource. Each such is monitored in Nodinite to help you make sure the Monitoring configuration is operational.
Here's an example of monitoring the 'Service Bus' Category as seen in a Nodinite Monitor View.
Example with a failing 'Subscription' for the Category 'Service Bus'.
This feature's background was that customers with deployed solutions by accident had business-impacting incidents due to people or automated deployments accidentally changed the name or even deleted the resource group.
| State | Status | Description | Actions | |
|---|---|---|---|---|
| Unavailable | Resource not available | Evaluation of the 'Azure Service Bus Subscription' is not possible either due to network or security-related problems | Review prerequisites and/or Configuration | |
| Error | Error threshold is breached |
|
Details Enable Disable | |
| Warning | Warning threshold is breached |
|
Details Enable Disable | |
| OK | Configuration is operational | Subscription is operational | Details Enable Stop |
Resource Group
For each configured Azure Subscription; You can manage the set of named Resource groups to include in the Monitoring. Each of these is presented by the Resource Group Category. Each such monitored configuration is presented as a Resource in Nodinite to help you make sure the Monitoring is operational.
Here's an example of monitoring the 'Resource Group' Category as seen in a Nodinite Monitor View.
Example with a failing 'Resource Group'.
This feature's background was that customers with deployed solutions by accident had business-impacting incidents due to people (usually developers), or automated deployments accidentally changed the name or even deleted the Azure Resource Group.
| State | Status | Description | Actions | |
|---|---|---|---|---|
| Unavailable | Resource not available | Evaluation of the 'Azure Resource Group' is not possible either due to network or security-related problems | Review prerequisites and/or Configuration | |
| OK | Configuration is operational | Resource group exists and is operational | Details |
Service Bus Configuration
The Service Bus Configuration Category lists each user-defined configuration. Each such monitored configuration is presented as a Resource in Nodinite to help you make sure the Monitoring configuration is operational.
Category 'Service Bus Configuration' selection as seen in a Monitor View
Monitor Resources of the Category using the Nodinite Monitor Views:
Example with failing connection with configured 'Subscription' for category 'Service Bus Configuration'
This feature's background was that customers with deployed solutions by accident had business-impacting incidents due to people or automated deployments accidentally changed the name or even deleted the resource group.
| State | Status | Description | Actions | |
|---|---|---|---|---|
| Unavailable | Resource not available | Evaluation of the 'Azure Subscription Configuration' is not possible either due to network or security-related problems | Review prerequisites and/or Configuration | |
| OK | Configuration is operational | Subscription configuration exists and is accessible | N/A |
Alert history for Azure Service Bus
During root cause analysis or other purposes, it might be helpful to understand how often your Azure Service Bus problems happen. If your Monitor View allows it, you can search for historical state changes for the provided time span, either for all your Azure Service Bus or individually. This topic is further detailed within the generic instructions on how to Add or manage Monitor View page.
 Search for alert history for all resources in the Monitor View |
 Alert history for the selected app |
Frequently asked questions
Use the troubleshooting guide to find the FAQ and answers to known problems.
How do I grant my users access to Azure Service Bus monitoring?
This is detailed in the User access to Azure Service Bus monitoring guide.
How do I enable monitoring of Azure Service Bus
To Monitor the Azure Service Bus; Check the Enable monitoring for Service Bus checkbox (default is checked). Additional configuration is required; Review the 'User access to Azure Service Bus monitoring' user guide for specifics.
The screenshot below is from the remote configuration form available from the Monitoring Agents administration page.
Example with monitoring for Azure Service Bus resources enabled.