Azure Service Bus is a messaging service on the cloud that is used to connect any application, device, or service running in the cloud to any other application or service.
As a result, it acts as a messaging backbone for applications available in the cloud or across any device.
Users can associate a Service Bus Queue to Serverless360 Business Application to accomplish the following operations.
The real challenge in dealing with Service Bus Queues/Topics in the Azure portal is no visibility on the messages. In real-time, there is an immense need to access and process the Service Bus messages to keep the business going.
Serverless360 solves this problem by allowing users to query the messages in Active-end or Dead-Letter queues, in a specific state such as the Peek or Deferred state, and by providing the message count and Sequence number to start retrieving from.
Not only these, but users can also perform queries on the retrieved messages to filter them based on their System and Custom properties, Dead-letter reason (For Dead-letters) which includes system provided reasons as well as custom error reasons.
Filtering can be done in the form of Json and text formats as well.
The below illustration shows retrieving messages in a Peek mode.
The below illustration shows retrieving messages in a Defer mode. This mode defers the number of messages provided in the Message Count, which can be accessed from the Deferred Active Messages and Deferred Dead-Letter tabs anytime.
To access a deferred message, it is required to know the message sequence number. With Serverless360, get access to all the messages in the deferred state without the need to know their sequence number.
|Peek mode||Defer mode|
|Messages will be peeked. This will not affect the active receivers of the active-end Queue.||Messages will be deferred. This will affect the active receivers of the active-end Queue.|
|The Delivery count of the message will not be increased||Delivery count of the message will be increased|
|Cannot perform delete operation||Can perform delete operation|
- Execute out-of-the-box queries on the retrieved messages using the system or custom properties.
- Filter messages by Enqueued time using AND/OR operators.
Save a query filter
The queries used for filtering can be saved with the help of Save button available next to Filter option. You can access all saved queries by clicking the Saved queries option at the top of the screen.
The default query can be defined so that it will be displayed for user convenience when retrieving messages from Service Bus Queue in any mode. Clicking on the Filter option will filter data based on the default query available.
- Users can update the status of the Service Bus Queue resource by clicking on the Update status option and selecting one among the list of available options.
- Users can also update the status of multiple Service Bus Queue resources by performing a bulk operation in the Service Bus Queue resource section.
Messages can be processed in a lot of ways as Serverless360 provides all capabilities that are lagging in many enterprise Service Bus management applications.
Below are the top capabilities for dealing with a Service Bus Queue:
- Repair & Resubmit
- View Message details
- View Message properties
- View Dead-letter reason and description
- Perform Automated tasks
There is a need for every application that uses Service Bus to resubmit a message that has gone into the dead-letter queue back to the same queue.
Serverless360 provides options to resubmit a single message or bulk of messages from the active-end or dead-letter back to the same queue, different queue, topic, or an API Endpoint.
The below illustration shows how easily users can resubmit messages.
Sending messages with the same message id to a Service Bus resource with duplicate detection enabled will result in the duplicate messages being ignored. Serverless360 allows users to regenerate message id manually or automatically while resubmitting messages.
Repair and Resubmit messages
Not only resubmitting but also repairing and resubmitting a message is always a requirement for applications using Service Bus in several use cases.
Serverless360 provides multiple options that users can use to repair and resubmit Service bus messages.
- Inline Repair and Resubmit single message
- Bulk Repair and Resubmit messages using Excel sheet
The below illustration shows repairing and resubmitting a single message directly from Serverless360.
The below illustration shows bulk repairing messages from Excel sheets and resubmitting them using Serverless360.
Save and Upload messages
Users can not only view messages but also download and upload them directly to Service Bus Queue.
Select the messages to download as a compressed (zipped) folder.
- Upload the messages in an Excel workbook using the template provided in the Upload section in the sidebar.
Backup and Delete messages
Deleting messages that are in a dead-letter queue for a long time, or messages that are not required anymore is a real-time business need.
Using Serverless360, messages from both active-end and dead-letter can be deleted simply by choosing the Delete option.
To avoid deleting a message by mistake, or to clear up the Queue but backup the messages in some other place, users can use the backup option to backup messages safely in an associated Storage Blob container before processing them.
In the Service Bus Queue section, users can create a really quick task to send messages to or purge messages from the source queue that is being explored.
The configuration created to run immediately can also be saved for future use in the Automated Tasks section.
Inline task to send messages
This feature allows users to quickly send messages to the queue by providing the following inputs:
- Message count
- Session Id/Partition Key (if enabled)
- User Properties
- Configuration name (if Save configuration is enabled)
The following illustration shows sending 10 messages to the Service Bus Queue.
Inline task to purge messages
This feature allows users to quickly purge messages from the queue by providing the following inputs:
- Message count (can be all or a specific number)
- Queue type (Active-end queue or Dead-Letter queue)
- Message Enqueued At time
- User Properties
- Configuration name (if Save configuration is enabled)
The following illustration shows purging 8 messages from a Dead-Letter enqueued at or before the specified date and time.
Task status can be viewed by navigating to the Automated Tasks section and switching to the Task history tab.
Users can use this feature to quickly create a task that runs immediately.
Navigate to the Automated Tasks section in Serverless360 to create a task with a more detailed configuration, schedule tasks to run at a specific time, or automate the task to run on the specified hours, days, and more.
Large applications that heavily rely on Service Bus cannot manually process messages all the time.
Service Bus Queue can send hundreds and thousands of messages in a short amount of time or process active and dead-lettered messages without the need for manual intervention using automated tasks.
The Automated Task feature of Serverless360 makes it possible to accomplish all these requirements.
Users now have access to a default Service Bus Queue Dashboard within the Service Bus Queue resource, allowing for enhanced data visualization and tracking of real-time data.
Users are provided with the following pre-defined Dashboard widgets, which can be customized to meet their specific needs.
1. Incoming Messages
2. Connections Opened vs Connections Closed
3. Overall Summary
4. Outgoing Messages
Users can monitor their Service Bus Queue resources by configuring the rules available for monitoring.
Navigate to the Monitoring section of the resource to configure the monitoring rules for Service Bus Queue.
Users can specify monitoring threshold values based on their needs.
When the monitoring rule type is a metric, selecting metric against metric rules is also an option.
- All the real-time properties of the associated Service Bus Queue can be viewed in table and JSON format directly from the Properties section.