← Return To Home

Azure Event Grid: Cab Availability Management Application

This blog talks about how Serverless360 can help with better managing and monitoring Azure Event Grid. Considering a real-time business orchestration, Cab availability management will let us understand how the business needs in managing and monitoring can be fulfilled using Serverless360. This article is mainly for DevOps Engineers, Support Engineers, Azure Developers, and Architects.

Manage and monitor Event Grid at the application context

Consider a scenario, A support person would need to know how the cab availability orchestration works and status of the entities in the orchestration instantly. Here comes the Service Map in Serverless360. With Service Map, user can easily construct a topology diagram of an orchestration and get to know the status of the Entity in near real-time based on the configured monitors.

Business Orchestration

Free download this blog as a PDF document for offline read.

View the Properties of the Event Grid Topic and Event Grid Subscription

View the properties like the Topic, Endpoint and Dead-letter Destination of an Event Grid Subscription or Subscription Name, Subscription Id for Event Grid Topics from Serverless360 itself. This will reduce the time spent on switching between the portal and Serverless360.

View the Properties

Process the Dead – Lettered events

In-Cab availability management scenario, the Event Grid Subscription has relay as its endpoint. When the relay attains the maximum number of listeners, the Event Grid cannot send events to the relay. In this case, those events will be dead-lettered into the configured storage blob, after the defined number of retries. Later, the listener count of the relay might get reduced, now the Event grid can send the events to the relay but those dead-lettered events in the storage blobs also need to be processed since they might be the business-critical events. To solve this huge challenge, Serverless brought in the Event processing with which user can view the event details, process the dead-lettered events to Event Grid topics or Repair & Reprocess the events to Event Grid topics.

Event Processing

Simulate the orchestration with automated activities

There will need to test cab availability orchestration build with Azure Event Grid. With Activities in Serverless360, User can send the events to the Event Grid topic to test the orchestration build with it. In Activities, it is possible to define the data, Event Type, Subject, Data version, and count. It is also possible to schedule the activities at the required time and date.

Activities

Monitor the Event Grid in various perspectives

Detect the Destination process duration of Event Grid Subscription, the success latency of the Event Grid Topic and more with Data monitor in Serverless360. This Data monitor is used to detect the performance, efficiency, latency of the entities in the orchestration with an extensive set of metrics. It also gives the historical record of alerts in a calendric view.

data monitor

Keep the stakeholders informed on the Event Grid status

Serverless360 supports 7 different notification channels through which the stakeholders can be kept informed on the status of the entities. Webhook notification channel can be used to integrate a custom cloud application which can create a ticket in the incident management system when an alert is triggered by Serverless360 monitor.

notification channels

Track the User Activities in a single place

Consider when multiple stakeholders working on this Cab availability management, one of the stakeholders might process the dead-letter events and other would dead-lettered those events for testing purpose. Here comes the challenge so there would be a need of tracking user activities in a single place. To solve this challenge, Serverless360 comes with the solution called Governance & Audit with which user can track who, when, and where the event has processed.

Governance Audit

One thought on “Azure Event Grid: Cab Availability Management Application”

Comments are closed.