- 4 minutes to read

Monitoring Azure Service Bus Topics and Subscriptions

Unlock real-time visibility and proactive control over your Azure Service Bus Topics and Subscriptions with Nodinite. The 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 Topics and 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 Topics 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.
Monitored Service Bus Topics
Here's an example of Nodinite Monitoring of Azure Service Bus Topics.

graph LR subgraph "Nodinite" roNI(fal:fa-code-commit Message Queueing Monitoring Agent)--- roMonitor[fal:fa-monitor-waveform Monitoring] end subgraph "Azure subscriptions" roMonitor --> |0..*| roS["fal:fa-credit-card Subscription"] end subgraph "Resource Groups" roS --> |0..*| roRG["fal:fa-object-group Resource Group"] end subgraph "Service Bus Namespaces" roRG --> |0..*| roNS("fal:fa-list Service Bus Namespace") end subgraph "Service Bus Topics" roNS --> |0..*| roSBT("fal:fa-list Service Bus Topic") end subgraph "Subscriptions" roSBT --> |0..*| roSBTQ("fal:fa-ear Subscription") end subgraph "Filters" roSBTQ --> |Match on Subject| roSBTQF1("fal:fa-filter Filter") end subgraph "Forward To Queues" roSBTQF1 --> |Match on Subject| roSBTQF1FQ1("fal:fa-list Forward To Queue") end

Mermaid 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 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:

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.
Service Bus Resources
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:
    Service Bus Topic Category

  • The Application name is based on physical deployment paths. This pattern guarantees uniqueness:

    • subscription name/resource group name/namespace name

Application Path Example
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
  • Evaluation of the 'Azure Service Bus Topic' is not possible either due to network or security-related problems
  • Specific topic not found
  • Specific namespace not found
 Review prerequisites
Error Error threshold is breached
  • Topic is disabled
  • Dead letter messages in Topic
  • No subscriptions (invalid configuration)
  • All subscriptions are disabled (invalid configuration)
 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

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.
Enable Monitoring
Example with monitoring for Azure Service Bus resources enabled.

Next step