Monitoring Azure Service Bus
The Nodinite Monitoring features for Azure Service Bus 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 page.
The agent auto-discovers your deployed Azure Service Bus resources in all accessible Resource Groups. Deploy new Azure Service Bus resources, and they will automatically get monitored and listed within your Monitor Views.
Monitoring Features
Below is a list of the Nodinite monitoring of the Azure Service Bus:
- Service Bus Queues
- List dead-letter
- Age verification
- Count (warning/error)
- The end-user can override global settings
- Service Bus Topics
- Configuration is operational (for example, at least one Subscription exists)
- List dead-letter
- Age verification
- Count (warning/error)
- The end-user can override global settings
- Service Bus Relay
- Resource groups
- Service Bus Configuration
- No changes to existing Azure deployments and no coding is required(!)
- Automatic Discovery
- The Nodinite Azure agents all use both the SDK and the Azure Rest API and offer you an automatic discovery of your Azure Service Bus resources. Sharing access to any individual queue 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
State evaluation
Each monitored 'Service Bus Queue' is displayed in Monitor Views within Nodinite as one Resource with its currently evaluated state. If you have 42 deployed Azure Service Bus, then you will have 42 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 Queues
All Azure ServiceBus queues belong to the 'Service Bus Queue' category:
The Application name is based on physical deployment paths. This pattern guarantees uniqueness:
- subscription name/resource group name/namespace name
Example of Application naming pattern providing uniqueness
Each monitored Service Bus Queue is a Resource and can have one of the following states at any given moment:
| State | Status | Description | Actions | |
|---|---|---|---|---|
| Unavailable | Resource not available | Evaluation of the 'Azure ServiceBus queue' is not possible either due to network or security-related problems | Review prerequisites | |
| Error | Error threshold is breached |
|
Edit thresholds Purge List messages List dead-letter |
|
| Warning | Warning threshold is breached |
|
Edit thresholds Purge List messages List dead-letter |
|
| OK | Within user-defined thresholds | Queue has NO not too many or too old messages according to user-defined thresholds | Edit thresholds Queue details List scheduled |
Resource groups
For each subscription; Manage the list of named Resource groups to include in the monitoring. Each of these named 'Resource groups' is listed by the Resource group Category. Each such monitored configuration is presented as a Resource in Nodinite to help you make sure the Monitoring configuration is operational.
Category 'Service Bus' selection as seen in a Monitor View
Resources of the Category can be monitored from within Monitor Views:
Example with failing 'Resource group'
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 'Resource Group' is not possible either due to network or security-related problems | Review prerequisites and/or Configuration | |
| Warning | Warning threshold is breached | The Resource Group has no Service Bus Namespaces | ||
| OK | Configuration is operational | Resource group exists and is accessible | [Details][RGInfo] |
Azure ServiceBus Subscription
Each unique namespace for the 'Service Bus' configurations are listed by the Category Service Bus. Each such monitored configuration is presented as a Resource in Nodinite to help you make sure the Monitoring is operational.
Category 'Service Bus' selection as seen in a Monitor View
Resources of the Category can be monitored from within Monitor Views:
Example with failing 'Subscription' for 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 Subscription' is not possible either due to network or security-related problems | Review prerequisites and/or Configuration | |
| OK | Configuration is operational | Namespace found in Subscription that still exists and is accessible | Details |
Service Bus Configuration
Each configuration is listed by the Service Bus Configuration Category. 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.
Resources of the Category can be monitored from within 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 useful 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 Azure Service Bus, the Message Queueing Monitoring Agent must be configured with the Enable monitoring for Service Bus checkbox checked (default is checked) further detailed in the 'User access to Azure ServiceBus monitoring' page.
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