Data Monitoring in Serverless360 – get alerts on any unprocessed/Left behind messages in your Queue/Topic Subscription
  • 05 Apr 2021
  • 2 Minutes to read
  • Contributors
  • Dark
    Light
  • PDF

Data Monitoring in Serverless360 – get alerts on any unprocessed/Left behind messages in your Queue/Topic Subscription

  • Dark
    Light
  • PDF

Data Monitoring in Serverless360 – get alerts on any unprocessed/Left behind messages in your Queue/Topic Subscription

When we build an Integration solution involving the Azure Service Bus, message flow plays a vital role. Applications connected with Service Bus Queue/Topic Subscription will pick up the messages and process them as defined. These are the most frequently made configurations with serverless architectures. There may be scenarios where our backend application may not be available for processing, and the messages can get stagnated in the Queue/Topic Subscription for a long time. Such situations will impact the business when the stagnated messages are left unattended. Monitoring the backend application for availability may not be a suitable solution for all businesses, as the backend application may be a custom solution, or the backend application may be handled by a third-party person as well. Thus, one of the most adaptable approaches would be to monitor whether the messages transmitted to the Queue or Topic Subscription is processing or not. This approach will give more control and flexibility as the Azure Service Bus will be residing inside their environment and reducing others' dependencies.

But the problem we face in implementing this solution is that: Native Azure Monitors cannot alert on any unprocessed messages. So, the question here is: How to achieve this use case?

Solution

Serverless360's Data Monitor can address this particular use case. Unlike other tools, Serverless360 is easy to implement and can issue consolidated alert reports. We can monitor resources based on available metrics within a specified time frame using Serverless360's Data Monitor. But this feature alone cannot solve our business use case. So, Serverless360 has built the capability to do metric versus metric comparison knowing the customer's challenges.

We can monitor resources by comparing two different metrics. To get an alert for any unprocessed message or left-behind messages, the user can leverage Serverless360's cross metric comparison available in the Data monitor.

Implementing the Solutions

In Serverless360's Data monitor, we can associate the required Queues and Topics. In the metrics page, we can choose the outgoing messages metric, and in the error threshold value, the user can type an incoming message and set the condition to lesser than (<).

Metric Vs Metric Configuration.png

After this setup, we can also define the monitor frequency. The maximum frequency can be one day, and the minimum is 15 minutes. Utilizing the monitor frequency, we can monitor the Queue/Topic Subscription at a regular interval. Depending on the business needs, we can configure the frequency and get the alert report in the configured frequency.

Monitoring frequncy.png

The above configuration will compare both the metrics in the given monitoring frequency. Alerts generated from Serverless360 will be a consolidated report. So, in a single Data Monitor, we can configure all the required Queues/Topic Subscription and get a single alert containing all the resources monitoring status.

Monitoring Report.png

Conclusion

Serverless360 not only helps to deal with this particular use case, but it also provides an Enterprise level solution for your Azure Serverless space. With minimal efforts, the organization can solve the challenges faced by users at any level.


Was this article helpful?