Event Grid Tasks
  • 02 Sep 2022
  • 2 Minutes to read
  • Contributors
  • Dark
    Light
  • PDF

Event Grid Tasks

  • Dark
    Light
  • PDF

Introduction

Event Grid Topics are created by the event publishers to forward the events to the destination. Event Grid Topics are the endpoints to which the source (publisher) sends the event.

Azure provides some system topics which can only be subscribed by the Event Grid Subscriptions. They belong to the event publishers, which are mainly the Azure services like Service Bus namespaces.

Custom Event Grid Topics can be created when the event publishers are not Azure services. For example, when a custom application has to send an event to a destination (say, a storage account blob), users can make use of Event Grid Topics.

It is also possible to create multiple Event Grid Subscriptions for the same Event Grid Topic so that all the destinations receive the event published to that event grid topic.

Sending events to Event Grid Topic

Consider a scenario where there are multiple Event Grid Subscriptions created for a single Event Grid Topic in a Business Process. There may be a need to verify whether the events sent to the Event Grid Topic is received by all the Event Grid Subscriptions.

Serverless360 provides a capability of sending the events to Event Grid Topics.

Events can be sent to the Event Grid Topics associated to the Business Application of Serverless360. It is also possible to define the following properties along with the actual event data:

Property Description
Subject Publisher-defined path to the event subject
Data Version The schema version of the data object. The publisher defines the schema version
Event Type One of the registered event types for this event source

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

Users can specify the following configurations to send events to an Event Grid Topic:

  • Event Data count - Total number of events to be sent (Maximum of 10,000 events).

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

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

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

Send events to EG topic.gif

Notifications

  • Users can now receive notifications when an Event Grid automated task is completed successfully.

  • The final sections of the Event Grid 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.

Event Grid notification.png


Was this article helpful?