- Updated on 26 Apr 2019
- 2 minutes to read
Why monitor Service Bus Queues?
In Serverless business applications, Service Bus Queues are used to support features those involve computation and processing behind the scenes on behalf of the service. When Service Bus Queue plays a critical role in the business application it becomes inevitable to monitor the same.
When a Service Bus Queue is associated with a Serverless360 Composite Application, it is possible to monitor Service Bus Queue in various perspectives using the monitors in Serverless360.
Monitor Service Bus Queue State
If the intention is to monitor the state, say the business demands the Queue to be always active, Serverless360 can monitor Queue state. By associating the Service Bus Queue to Status Monitor or Threshold Monitor, it is possible to monitor the state, compare the current state against the expected state and alert through configured notification channels.
Monitor Service Bus Queue Properties
It is also possible to monitor the Queue based on the following set of properties:
• Transfer Dead Letter Message Count
• Size in Bytes
• Message Count
• Scheduled Message Count
• Active Message Count
• Dead Letter Message Count
• Transfer Message Count
Service Bus Queue can be monitored on multiple properties mentioned above with appropriate warning and threshold values. Please refer extensive documentation on Status Monitor and Threshold Monitor to choose the right monitor to meet your business need.
Monitor Service Bus Queue on its Metrics
If the intention is to understand the message flow, reliability of the Service Bus Queue then the choice should be a Serverless360 Data Monitor. Data Monitoring can be configured for a Service Bus Queue on an extensive set of metrics. Service Bus Queue data monitoring with appropriate warning and threshold values can be set as in represented below:
Data Monitoring Recommendations
The table below lists down the combination of metrics to monitor the Service Bus queue in various perspectives using Serverless360 Data Monitor.
|Monitoring Purpose||Metrics to Choose|
|Check if the Service Bus Queue is available. Please refer this article on ‘Monitoring Azure Service Bus Queue Availability’||Server Errors (Count), User Errors (Count), Size (Bytes)|
|Monitor Incoming Requests over a time duration||Incoming Requests (Count)|
|Monitor Incoming and Outgoing Messages over a time duration hence check if Upstream and downstream applications are active||Incoming Messages (Count), Outgoing Messages (Count)|
|Check if applications interacting with the Service Bus Queue are generating any exceptions||User Errors (Count)|
|Monitor Throttled Requests over a time duration||Throttled Requests (Count)|
|Check if expected number of messages are being processed by the interacting applications. Check message count by type||Count of messages (Count), Count of active messages (Count), Count of dead-lettered messages (Count), Count of scheduled messages (Count)|
|Detect anomaly in abnormal increase in Queue size||Size (Bytes)|
Data Monitor can be configured with various combination of metrics to meet various monitoring requirements.