In this article: 

  1. Create and delete Azure Service Bus Queues
  2. View and edit properties of the Azure Service Bus Queue
  3. Import Azure Service Bus Queues
  4. Retrieve a message from Azure Service Bus Queue
  5. View and resubmit dead letter messages from Azure Service Bus Queue
  6. View deferred dead letter messages from Azure Service Bus Queue
  7. Purge Messages for Azure Service Bus Queues
  8. Getting Queue URL and Shared Access Policy
  9. Sending messages to Queues
  10. Scheduling bulk messages and Dead Letter Messages
  11. Dead Letter Queue - volume analytics

Create and delete Azure Service Bus Queues

Service Bus queues are part of a broader Azure messaging infrastructure that supports queuing as well as publish/subscribe, and more advanced integration patterns that may span multiple communication protocols, data contracts, trust domains, and/or network environments. In Queues, the messages are typically expected to be received and processed by the receivers in the order in which they were added to the queue, and each message is received and processed by only one message consumer. ServiceBus360 allows the users to perform CRUD operations on Queues from within the portal. 

To create an Azure Service Bus Queue in ServiceBus360:

  1. Log in to the 'ServiceBus360 account'
  2. Click the 'Management Stack' icon in the left-top corner of the screen and select 'Service Bus' option from the menu
  3. Click the 'Manage' icon inline with namespace to be selected
  4. Click the 'Queues' icon in the left navigation panel and click the 'Create' button to open the 'Create-Queue' blade
  5. Enter the Queue path and configure the Queue properties like max queue size, batch operation, dead-lettering on message expiration, partitioning, duplicate deletion, session, and express. 
  6. With ServiceBus360 you can also auto forward the messages to other Queues/Topics by enabling the toggle button against 'Forward To' option. Select the radio button and choose the respective Queues/Topics to forward the messages.
  7. You can also forward the dead-lettered message to other Queues/Topics by enabling the toggle button against 'Forward Dead-Lettered Messages To' option. Select the radio button and choose the respective Queues/Topics to forward the dead-letter messages.
  8. Click 'Next' to set the Queue additional properties like default message time to live, auto delete on idle, lock duration, duplicate detection history time window, and max delivery count. 
  9. Enter user description and click 'Save' to create an Azure Service Bus Queue from ServiceBus360
  10. To delete Queue(s) from ServiceBus360, click the 'Queues' icon in the left navigation panel and select the checkbox(s) inline with the Queues to be deleted and click the 'Delete' button. Enter the reason for deleting the queue to confirm the action and click 'Continue'.

View and edit properties of the Azure Service Bus Queue

When messages accumulate in one of the queues, you can view the queue properties to get more information about the possible causes of this accumulation. When the Queues list is generated in ServiceBus360, the screen contains a Properties icon against each queue that will contain the properties of the queue. All information in the queue properties blade will be populated from the Azure portal and the values can be edited in ServiceBus360. To view/edit the queue properties in ServiceBus360:

  1. Log in to the 'ServiceBus360 account'
  2. Click the 'Management Stack' icon in the left-top corner of the screen and select 'Service Bus' option from the menu
  3. Click the 'Manage' icon inline with namespace to be selected
  4. Click the 'Queues' icon in the left navigation panel. The Queues dashboard displays the list of Queues available in the namespace. 
  5. Click the 'Extras (ellipses)' icon against the Queue that you wish to view the properties
  6. Click the 'Properties' link in the drop-down. The Queue properties blade will display the Queue properties.
  7. Click 'Edit' to edit properties like:
    1. Batched operation
    2. Dead-Lettering on message expiration
    3. Max delivery count
    4. Status
    5. Forward message to
    6. Forward dead-letter messages to
    7. Default message time to live
    8. Auto delete on idle
    9. Lock duration
    10. Duplicate detection history time window
  8. Enter the reasons for the modification and click 'Save' to complete the process

Import Azure Service Bus Queues

In this section, we will see the different options to import an Azure Service Bus Queues from one namespace to another using ServiceBus360. Let's consider a scenario, ACME corporation has created and configured the settings for a Queue in their test environment and wants to replicate the same in the development environment, in this scenario, the only option is to recreate the Queues with the same settings either in the Azure portal or in Service Bus Explorer. Obviously, this is a time-consuming process, ServiceBus360 provides a simple solution by allowing the users to import the Queues between namespace to make the process the easy.

  1. Log in to the 'ServiceBus360 account'
  2. Click the 'Management Stack' icon in the left-top corner of the screen and select 'Service Bus' option from the menu
  3. Click the 'Manage' icon inline with namespace to be selected
  4. Click the 'Queues' icon in the left navigation panel. Click the 'Import' button to open the 'Import Entities' blade
  5. Select 'Import from a file' to import the Queues that are exported from Service Bus Explorer as XML file
    1. Click the Browse button to open the file location
    2. Select the file and click 'Proceed'
  6. To import from another namespace, click the checkbox against 'Import from other namespaces' option 
    1. Choose the namespace from the drop-down and select the Queues to import
    2. Click the 'Proceed' button to complete the process
  7. The Queues will be imported along with the configurations

Retrieve a message from Azure Service Bus Queue

ServiceBus360 allows users to execute queries to retrieve messages from Queues in 'peek lock' mode. When the query is executed from the UI, ServiceBus360 triggers a service call that retrieves the list of messages in peek lock mode. In addition, the service call will retrieve other information related to the message such as sequence number, size, label, enqueued time, expiry time, message details and properties. In ServiceBus360, the users can retrieve both active and dead letter messages. Follow the steps as shown below to retrieve messages from queues in ServiceBus360:

  1. Log in to the 'ServiceBus360 account'
  2. Click the 'Manage' icon on the Composite Application with which the Queue is associated 
  3. Click the 'Queues' tab in the Composite Application-group
  4. Click on the Queue name to retrieve the message or click the 'Operations' icon against Queue that you wish to retrieve the message.
  5. Click 'Messages' tab. Enter the number of messages to be retrieved (maximum allowed limit is 100) and the Sequence number. If no Sequence Number is mentioned, ServiceBus360 returns the number of messages from the sequence number from the top of the Queue.
  6. Click the 'Get' button to retrieve the messages
  7. Click the 'Properties' icon against the message to view the message properties
  8. Click the 'Details' icon against the message to view the message details

View and resubmit dead letter messages from Azure Service Bus Queue

ServiceBus360 allows users to execute queries to retrieve dead letter messages from Queues in both 'peek lock' and 'defer' mode. Only the dead letter messages that are not deferred at the time of receiving will be retrieved. These messages will be deferred and then not be available to receive by other applications. Use ServiceBus360 to resubmit or delete them later. In addition, the service call will retrieve other information related to the message such as message id, sequence number, size, label, error reason, enqueued time, expiry time, message details and properties. Follow the steps as shown below to retrieve dead letter messages from queues in ServiceBus360:

  1. Log in to the 'ServiceBus360 account'
  2. Click the 'Manage' icon on the Composite Application with which the Queue is associated 
  3. Click the 'Queues' tab in the Composite Application-group
  4. Click on the Queue name to retrieve the message or click the 'Operations' icon against Queue that you wish to retrieve the message.
  5. Click 'Deadletter messages' tab to retrieve messages from the Queue
  6. Select between the two options - either retrieve messages in peek lock mode or defer mode
  7. When peek lock mode is chosen to retrieve the message: 
    1. Enter the number of messages to be retrieved (maximum allowed limit is 100) and the Sequence number. If no Sequence Number is mentioned, ServiceBus360 returns the number of messages from the sequence number from the top of the Queue.
    2. Click the 'Get' button to retrieve the messages
    3. Click the 'Properties' icon against the message to view the message properties
    4. Click the 'Details' icon against the message to view the message details
  8. When defer mode is chosen to retrieve the message:
    1. Enter the number of messages to be retrieved (maximum allowed limit is 100) When the dead letter messages are retrieved in defer mode, these messages will not be available for receiving by other applications. These messages will be moved to Deferred Deadletter tab and the user can access the messages from the Deferred Deadletter tab.
    2. Click the 'Get' button to retrieve the dead letter messages in defer modeThe user can filter the messages for the parameters like Header Size Exceeded, TTL Expired Exception, Session Id is Null, Max Transfer Hop Count Exceeded and any other error description.
    3. The user can resubmit the retrieved messages by selecting the checkbox against the messages, and click 'Resubmit' to open the 'Resubmit messages from Queue' blade.
    4. Select the Queues and click 'Proceed'. The system will prompt a confirmation message "Would you like to Resubmit the message? Target Entity: Queue - XXXXX". 
    5. Click 'Continue' to resubmit the message(s). The system will display the success/failure notification.
    6. To delete the selected messages click the Delete button  

View deferred dead letter messages from Azure Service Bus Queue

The dead letter messages that are retrieved in defer mode will be moved to the Deferred Deadletter tab. The user can either view the message details, properties, error or resubmit/delete the messages from this Deferred Deadletter section.

  1. Log in to the 'ServiceBus360 account'
  2. Click the 'Manage' icon on the Composite Application with which the Queue is associated 
  3. Click the 'Queues' tab in the Composite Application-group
  4. Click on the Queue name to retrieve the message or click the 'Operations' icon against Queue that you wish to retrieve the message.
  5. Click 'Deferred Deadletter' tab to retrieve messages from the Queue
  6. Enter the number of messages to be retrieved (maximum allowed limit is 100)
  7. When the dead letter messages are retrieved in defer mode, these messages will not be available for receiving by other applications. These messages will be moved to Deferred Deadletter tab and the user can access the messages from the Deferred Deadletter tab.
  8. Click the 'Get' button to retrieve the dead letter messages in defer mode
  9. The user can filter the messages for the parameters like Header Size Exceeded, TTL Expired Exception, Session Id is Null, Max Transfer Hop Count Exceeded and any other error description.
  10. The user can resubmit the retrieved messages by selecting the checkbox against the messages, and click Resubmit to open the Resubmit messages from Queue blade.
  11. Select the Queues and click 'Proceed'. The system will prompt a confirmation message "Would you like to Resubmit the message? Target Entity: Queue - XXXXX".
  12. Click 'Continue' to resubmit the message(s). The system will display the success/failure notification.
  13. To delete the selected messages click the 'Delete' button

Purge messages for Azure Service Bus Queues

You cannot delete an individual message from a Queue. Instead, you can purge all messages to completely clear the contents of the queue. To purge the messages in ServiceBus360:

  1. Log in to the 'ServiceBus360 account'
  2. Click the 'Manage' icon on the Composite Application with which the Queue is associated 
  3. Click the 'Queues' tab in the Composite Application-group
  4. Click the 'Extras (ellipses)' icon against the Queue that you wish to purge and click "Purge Message'
  5. Set date and time to purge messages that are enqueued at or before the selected time. Messages arriving after this time will not be affected by this activity.
  6. Select the Message State, say, Active indicates - Messages from Active Queue and dead-letter indicates messages from dead letter Queue
  7. Set this value to purge defined count of messages enqueued at or before the set time, even if there are more messages.
  8. Click Purge to delete all the messages

Getting Queue URL and Shared Access Policy

When you create a new queue, you must specify a queue name that is unique within the scope of all your queues. Azure Service Bus assigns each queue you create an identifier called a queue URL that includes the queue name and other components. Whenever you want to perform an action on a queue, you provide its queue URL.

  1. Log in to the 'ServiceBus360 account'
  2. Click the 'Manage' icon on the Composite Application with which the Queue is associated 
  3. Click the 'Queues' tab in the Composite Application-group
  4. Click the 'Extras (ellipses)' icon against the Queue that you wish to get the details
  5. You can get the Queue URL, dead letter queue URL and Shared access policy details from the drop down

Sending messages to Queues

Sending messages to a Queue or Topic is similar to sending events to an Event Hub. ServiceBus360 has the capability to send events/messages immediately from the list of Queues/Topics by creating an Activity Configuration. Activity Configuration has been introduced considering the re-usability.

What is an Activity?

Activities allow you to push sample messages into desired Queues or Topics. It can be used mainly for testing purposes. Ex: Sending 5000 sample messages into a Queue with think time, batches, multiple threads etc. You can have multiple activities configured and executed them either instantaneously or via a schedule.


ServiceBus360 has the option to send messages from the listed Queues/Topics by simply entering the desired values and hit the Send button. As every task is processed in the cloud – it will queue the task to a certain queue from where it will be picked up and processed. However, the processing is fast enough and you will be able to see the in-progress activity in “In Progress” tab. Sometimes you may not find an activity in “In Progress” tab if the number of events is too small. As the process is quick – the process might be completed momentarily.

To send messages instantly:

  1. Log in to the 'ServiceBus360 account'
  2. Click the 'Manage' icon on the Composite Application with which the Queue is associated 
  3. Click the 'Queues' tab in the Composite Application-group
  4. Click the 'Extras (ellipses)' icon against the Queue
  5. In the 'Send Message' blade, enter the message, message count, and other custom properties. Click the 'Save Configuration' checkbox, enter a friendly name to save the configurations for future use.
  6. Click the Send button to send the Message

Scheduling bulk messages and dead letter messages

ServiceBus360 users also have the option to schedule activities to run at a specified time by creating an Activity Configuration. To create an Activity Configuration:

  1. Log in to the 'ServiceBus360 account'
  2. Click the 'Manage' icon on the Composite Application with which the Queue is associated 
  3. Click the 'Activites' icon in the left navigation pane and select 'Service Bus'
  4. In the Activities screen, click the 'Create' button and select the 'Send Message Activity' option from the drop-down
  5. The user has the option to configure an Activity at three levels. Enter the basic details like Activity Name,  Message, and Custom Properties. Click 'Next'.
  6. Select the options between Queues or Topics and enter other details like the Send Batch, Think Time, Task Count and Message Count. Additionally, you can configure the System Properties
  7. To initiate the process immediately click the checkbox – “Initiate Activity Immediately after you save”, which allows starting the activity as soon the activity configuration is saved.
  8. In the Schedule activity blade, you can configure the activity for a select date and time, either recurring or a one-time activity.
  9. Click 'Save' to create an activity configuration. The play button helps you initiating an activity of the Activity Configuration.You can view the in-progress activity details by clicking the “info” icon under the In Progress tab. Also, you can delete an ongoing activity from the In Progress tab.

Scheduling bulk dead-letter Activity Configuration

  1. Log in to the 'ServiceBus360 account'
  2. Click the 'Manage' icon on the Composite Application with which the Queue is associated 
  3. Click the 'Activites' icon in the left navigation pane and select 'Service Bus'
  4. In the Activities screen, click the 'Create' button and select the 'Dead-Letter Activity' option from the drop-down
  5. The user has the option to perform operations like:
    1. Resubmit: Keep the source message. Submit a copy of message to the destination queue
    2. Resubmit & Delete: Submit a copy of message to the destination queue and delete the source message
    3. Delete: Simply delete the message from the DLQ
  6. Select the From Dead-Letter Queue, To Queue and the Dead Letter Reason from the drop-down
  7. You can choose the messages based on the Enqueued time (this is an optional parameter) and set the Message Count 
  8. To initiate the process immediately click the checkbox – “Initiate Activity Immediately after you save”, which allows starting the activity as soon the activity configuration is saved.
  9. Click 'Save' to create an activity configuration. The play button helps you initiating an activity of the Activity Configuration.You can view the in-progress activity details by clicking the “info” icon under the In Progress tab. Also, you can delete an ongoing activity from the In Progress tab.

Dead Letter Queue - volume analytics

Analytics is an integrated module available ServiceBus360 that lets you set up real-time analytic computations on Azure ServiceBus Queues. ServiceBus360 Analytics offers a visual display of the most important performance counters that are consolidated and arranged on a single screen so that the information can be monitored at one glance.

What can I do with ServiceBus360 Analytics

Use ServiceBus360 Analytics to examine the volume of dead letting in Queues, extract information from last 24 hours to 7 days, and look for charts, dead letter reasons, and relationships using the Queues Analytics. Based on what's in the data, you can plan and perform various operations like resubmit, purge etc. For example, you might raise alerts, feed information to a reporting manager, or store data for later investigation.

How does Analytics work in ServiceBus360

In this section, you will learn how to use ServiceBus360 Analytics to get real-time insights from your Azure Service Bus Queues. Analytics is an inbuilt tool in ServiceBus360 with pre-configured widgets for Dead-Letter Queues, the data is represented in two different graphs (pie chart and bar chart) segregated based on the dead letter reason. The bar chart helps you to analyze the dead letters over a time period, the user can choose a time period between last 24 hours to 7 days. In the Free plan, a user can enable Analytics for any one of the available Queue from the associated messaging namespace. To enable and view Analytics data for a Queue in ServiceBus360:

  1. Log in to the 'ServiceBus360 account'
  2. Click the 'Manage' icon on the Composite Application with which the Queue is associated 
  3. Click the 'Queues' tab in the Composite Application-group
  4. Toggle on the Analytics button against the Queue(s) that you wish to enable Analytics
  5. Click the 'Analytics' icon to open the Queue-Analytics screen. The system will need at least 1 hour of data collection time to display the data in the Analytics graph
  6. You can see two pre-configured widgets representing the Analytics data
  7. The pie chart displays the dead letter by reason and the bar chart shows the dead letter by reason over time (last 24 hours by default) and can be adjusted to display last 7 days data

Analytics screen auto freshes every 60 seconds.