- 6 minutes to read

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 in the Managing Azure Service Bus page.

The agent auto discovers your deployed Azure Service Bus resources in all accessible Resource Groups. Simply deploy new Azure Service Bus resources and they will automatically get monitored and listed within your Monitor Views

List of example Resources

Monitoring Features

List of resources that can be monitored by using this agent

  • Service Bus Queues

  • Service Topics

  • Service Bus Relay

  • List dead-letter

  • Resource groups

  • Service Bus Configuration

  • Age verification

  • Count (warning/error)

  • Per queue setting can be overridden from default values

  • No coding required(!)

  • Automatic Discovery

    • Nodinite Azure agents make use of the SDK and the Azure Rest API and offer you an automatic discovery of your Azure Service Bus queues. 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.
ServiceBusResourcesAsResources
Live overview with different states summarized in a pie chart

The evaluated state may be reconfigured using Expected State override setting that exists on every Resource within Nodinite.

Azure Service Bus Queues

  • All Azure ServiceBus queues belongs to the 'Service Bus Queue' category:
    Service Bus Queue Category

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

    • subscription name/resource group name/namespace name

ApplicationPathExample
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 If the Azure Service Bus can't be evaluated either due to network or security-related problems Review prerequisites
Error Error threshold breached
  • Queue has to many or too old messages according to user-defined thresholds
  • Dead letter messages in queue
Edit thresholds
Purge
List messages
List dead-letter
Warning Warning threshold breached
  • Queue has to many or too old messages according to user-defined thresholds
  • Dead letter messages in queue
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

Within each subscription you can name which Resource groups to include in monitoring. Each of these named 'Resource groups' are listed by the Category Resource group where each such monitored configuration is represented as a Resource in nodinite to help you make sure monitoring works at all times.

Resource group monitoring
Category 'Service Bus' selection as seen in a Monitor View

Resources of the Category can be monitored from within Monitor Views:
ResourceNotAvailable
Example with failing 'Resource group'

The background for this feature 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 If the Resource group can't be evaluated either due to network or security-related problems Review prerequisites and/or Configuration
OK Configuration is operational Resource group exists and is accessible Details

Azure ServiceBus Subscription

Each unique namespace for the 'Service Bus' configurations are listed by the Category Service Bus where each such monitored configuration is represented as a Resource in nodinite to help you make sure monitoring works at all times.

Service Bus monitoring
Category 'Service Bus' selection as seen in a Monitor View

Resources of the Category can be monitored from within Monitor Views:
ResourceNotAvailable
Example with failing 'Subscription' for category 'Service Bus'

The background for this feature 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 If the namespace within a subscription configuration can't be evaluated 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 Category Service Bus Configuration where each such monitored configuration is represented as a Resource in nodinite to help you make sure monitoring works at all times.

Configuration monitoring
Category 'Service Bus Configuration' selection as seen in a Monitor View

Resources of the Category can be monitored from within Monitor Views:
ResourceNotAvailable
Example with failing connection with configured 'Subscription' for category 'Service Bus Configuration'

The background for this feature 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 If the subscription configuration can't be evaluated 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 for other purposes it might be useful to understand how often problems with your Azure Service Bus happens. 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

Other common problems and FAQ for the Message Queueing Monitoring Agent can be found in the troubleshooting user guide.

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 image below was taken from the remote configuration form available from the Monitoring Agent Configuration administration page.
EnableMonitoring
Example with monitoring for Azure Service Bus resources enabled


Next step