- 08 Aug 2023
- 3 Minutes to read
Event Grid Tasks
- Updated on 08 Aug 2023
- 3 Minutes to read
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, users can use Event Grid Topics when a custom application has to send an event to a destination (say, a storage account blob).
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 multiple Event Grid Subscriptions are created for a single Event Grid Topic in a Business Process. There may be a need to verify whether all the Event Grid Subscriptions receive the events sent to the Event Grid Topic.
Serverless360 provides the capability of sending the events to Event Grid Topics.
Events can be sent to the Event Grid Topics associated with the Business Application of Serverless360. It is also possible to define the following properties along with the actual event data:
|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 for traditional line-by-line event delivery and 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 the 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 the event delivery by waiting for the specified time after sending an event or batch (If configured).
Process dead-letters in Event Grid Subscription
With Serverless360, dead letters in an Event Grid Subscription can be easily managed and processed based on business requirements.
It is necessary to associate the corresponding Event Grid Topic, Event Grid Subscription, and Storage Blob container to the Business Application to process the events.
Serverless360 provides three types of configuration for processing dead letters in Event Grid:
- Resubmit messages - a copy of the source event will be sent to the Event Grid.
- Resubmit and Delete messages - A copy of the source event will be sent to the Event Grid and deleted from the blob container.
- Delete messages - the events will be deleted from the blob container.
Users can process all available dead-lettered events or provide a time range to process only a specific set of events.
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 include 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.