Business Activity Monitoring in Serverless360 With Real-Time Scenarios
This blog gives some interesting use cases of Business Activity Monitoring in Serverless360 using the example of a cab booking management system.
Join the DZone community and get the full member experience.Join For Free
This blog gives some interesting use cases of Business Activity Monitoring in Serverless360 using Cab Booking Management System. Let's take the booking scenario of this system backed with the Azure Serverless services and see how the business activity monitoring in Serverless360 will be useful in detecting the exceptions and tracking the custom properties of the messages flowing through the business process.
The above is a Cab booking application built with Azure Serverless. Consider a business user who would need to track message flows through every stage in the above business activity. They should be informed of any exception in the business transaction along with the reasons behind the failure. A business development manager would need to have analytic information on the booking trends at various locations.
Serverless360 BAM can serve the needs of business users. It is possible to track the business process, its transactions, and the stages of the orchestrations.
Tracking the Business Properties
In the cab booking application, we need to be able to track the Driver Id, User Id, and Location. By configuring the necessary properties while creating the business process, these can all be tracked in the BAM section.
These properties can be tracked at every stage of the transaction and even at the business process level. From this, we can learn how the data has changed at every stage. Along with the tracked properties, it is also possible to be aware of the status of every stage and hence the transaction.
From the above picture, it is so clear that even a sales/support person can easily understand and track the business data flowing through the Azure services.
Reprocessing Failed Business Processes
Consider a scenario where a user booked a cab and a driver was assigned. The driver went offline soon after the booking, thus the transaction failed at the driver validation stage of the transaction. To restore this transaction and complete the booking, another available driver should be assigned.
With the help of Reprocessing, a salesperson can change the required data and reprocess the message to the configured reprocess stage.
When there are multiple business processes being tracked in the BAM, there is a need for some efficient filtering mechanism to stay focused. With search queries in BAM, users can easily filter the business processes from various perspectives. In addition to query filtering, it also possible to filter based on the time interval.
Users can also save the query and use it for monitoring and analytics.
Consider a business development manager who needs to track the business trends at various locations or the number of bookings in the last 30 days to make strategic business decisions like expanding at a specific location. With the help of BAM analytics in Serverless360, users can see the visualization of the data as widgets based on the configured queries.
In the above image, booking trends on a location, booking trends at various locations, and the number of booking in the last 30 days have been visualized with help of BAM Analytics. It is also possible to create a number of widgets of any size and dashboards as per the requirements.
Business Process Monitoring
Consider a salesperson would needs an alert when the count of failed transactions goes beyond a certain limit at a location or an alert whenever there is an exception. To achieve this functionality, they will need a powerful monitoring tool that works from various perspectives. Serverless360 comes with the out-of-the-box monitoring solutions for monitoring business processes based on queries and exceptions, called Business Process Monitor. It is also possible to view the historical record of alert reports in a calendar view.
Business Activity Monitoring in Serverless360 solves huge challenges in end-to-end tracking of messages flowing through the business process and the need for analytics. It reduces the total cost of pwnership and reduces the effort spent on building solutions to do end-to-end tracking by 5%.
Published at DZone with permission of Madhavan kovai. See the original article here.
Opinions expressed by DZone contributors are their own.