Monitoring Azure Service Bus Topic Subscriptions
Unlock real-time visibility and proactive control over your Azure Service Bus Topic Subscriptions with Nodinite. The Nodinite Message Queueing Monitoring Agent empowers integration experts to detect bottlenecks, automate alerts, and resolve issues instantly—ensuring seamless, reliable system integration and maximum uptime.
On this page, you will learn how to:
✅ Monitor Azure Service Bus Topic Subscriptions with no coding required
✅ Automatically discover and visualize all resources in your environment
✅ Detect bottlenecks, dead letters, and configuration issues before they impact business
✅ Take Remote Actions to resolve issues directly from Nodinite
The Nodinite Monitoring features for Azure Service Bus Topic Subscriptions ensure you get alerts for performance issues, message stockpiling, and provide remote actions to resolve dead letter messages and more.
This section explains what is monitored, how Nodinite translates data into actionable insights, and how you can use remote commands (Actions) to swiftly manage problems. See Remote Actions and the Managing Azure Service Bus Topic page for more details.
Nodinite auto-discovers deployed Azure Service Bus Topics and Subscriptions from your named Resource Groups. These are presented as Resources in Monitor Views.
Here's an example of Nodinite Monitoring of Azure Service Bus Topics.
Diagram: How Nodinite discovers and monitors Azure Service Bus Topics, Subscriptions, and related resources.
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 Topic Subscriptions. Sharing access to any individual Topic 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.
State evaluation
Each monitored '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 Topic Subscriptions, then you will have 11 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 Subscription States
All Azure Service Bus Topics belong to the 'Service Bus Topic Subscription' 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, for a full list of Actions, please see the Available Actions section below.:
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 Subscription is operational | Edit thresholds Details Enable Disable |
Available Actions
The following actions are available for managing Azure Service Bus Topic Subscriptions (and some are identical for Queues):
- Details – View essential information about the selected Service Bus Topic Subscription.
- Edit thresholds – Configure monitoring thresholds for the selected queue.
- Enable – Enable a Service Bus Queue that is currently disabled.
- Disable – Disable a Service Bus Queue that is currently enabled.
- Resubmit and Delete All Dead Letter Messages – Resubmit and delete all dead letter messages in the sub queue.
- List Active Messages – View all messages in the active sub queue.
- Download - Download the message.
- View/Repair - View and repair the message.
- Delete - Delete the message.
-
- Purge by Session ID - Purge all messages with the same session ID as the selected message.
- Move to Dead Letter - Move the message to the Dead-letter sub queue.
- Resubmit - Resubmit the message to the queue.
- Resubmit & Delete - Resubmit the message to the queue and delete the original message.
- List Dead Letter Messages – View all dead letter messages in the queue.
-
- Download - Download the dead letter message.
- View/Repair - View and repair the dead letter message.
- Delete - Delete the dead letter message.
- Resubmit - Resubmit the message to the active sub queue.
- Resubmit & Delete - Resubmit the message to the active sub queue and delete the original message.
- Resubmit to Source - Resubmit the dead letter message to Source.
- Resubmit to Source and Delete - Resubmit the dead letter message to Source and Delete it.
- Purge Messages (Active) – Purge all active messages from the active sub queue.
- Purge Dead Letter – Purge all dead letter messages from the dead letter sub queue.
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.
![]() |
![]() |
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.