Service Bus tasks
  • 04 Oct 2022
  • 3 Minutes to read
  • Contributors
  • Dark
    Light
  • PDF

Service Bus tasks

  • Dark
    Light
  • PDF

Introduction

Many enterprises use Service Bus resources to communicate between different services. As a part of integrating the services, it is important to ensure that the message flow across the services is healthy.

Serverless360 overcomes this problem by automating the process of resubmitting and deleting messages to and from Service Bus resources, as well as sending messages to a Service Bus resource in a variety of ways.

Serverless360 enables the configuration of three types of tasks:

  • Send Service Bus Messages
  • Process Service Bus Messages
  • Process Service Bus Dead-Letter

Send Service Bus messages

As part of QA/Development, users of Service Bus integration frequently need to test the system integration by producing test messages to be transmitted to Azure Service Bus entities for performance testing or load testing.

Delaying Service Bus message delivery is a testing requirement not only for traditional line-by-line message delivery, but also for several other approaches such as parallel processing.

Users can specify the following configurations to send messages to a Service Bus Queue or Topic:

  • Message count - Total number of messages to be sent (Maximum of 10,000 messages).

  • Task count - Speeding up the delivery by running tasks in parallel (Maximum of 10 tasks). For example, specifying message count as 100 and task count as 2 allows the Automated task to send 50 messages in one task, and another 50 messages in another task running parallely, thereby speeding up the delivery.

  • Batch count - Messages can also be sent as batches (Maximum batch size of 10).

  • Think time - Slows down the message delivery by waiting for the specified time after sending a message or batch (If configured).

SB send message.gif

Process Service Bus messages

Users can process existing messages in a Service Bus Queue or Topic Subscription in addition to sending direct messages.

Serverless360 provides three types of configuration for processing Service bus messages and Dead-letters:

  • Resubmit messages - A copy of the message from the source Queue or Topic Subscription will be sent to the destination Queue or Topic.

  • Resubmit and Delete messages - A copy of the message from the source Queue or Topic Subscription will be sent to the destination Queue or Topic, and the message in the source Queue or Topic Subscription will be deleted.

  • Delete messages - Messages in the selected Queue or Topic Subscription will be deleted.

Messages can be processed based on the following filters:

  • Message count - The number of messages to be processed.

  • Message Enqueued date range - Only messages enqueued at or before the specified date range will be processed on specifying the date range when Customize date range for the configuration checkbox is enabled.

  • Message Enqueued time span - Only messages enqueued at or before the specified time span will be processed on specifying the time span when Customize date range for the configuration checkbox is enabled.


  • Dead-letter reason (Applicable for Processing Dead-letter) - Restrict the task to process only the messages dead-lettered due to a specific dead-letter reason.

Filtering is not supported in Resubmit-and-Delete and Delete message tasks for Partitioning-enabled resources.

Active message processing.gif

Dead letter message processing.gif

Notifications

  • Users can now receive notifications when a Service Bus Automated Task is completed successfully.

  • The final sections of the Service Bus Automated Task configuration blade includes the notification configuration section, where users can configure the desired configured Notification channels and email address(es) to receive notifications for a group or individually.

  • All the configured Notification channels will be listed in this section.

  • Multiple email addresses can also be provided so that a group of users can get notifications and stay in touch.

Send message - notification.png

Process active message - notification.png

Process dead-lettered message - notification.png

Key Benefits

Users can benefit from a variety of other features while processing messages, including:

  • Backing up messages in an associated Storage Blob Container. (Back up path will be available in Details section of Task history)

  • Auto-regenerating message ids while resubmitting messages to a resource with Duplicate detection property enabled, to avoid message loss.

  • Resubmitting messages to an API Endpoint.


Was this article helpful?

What's Next