- 25 Sep 2020
- 2 Minutes to read
- Updated on 25 Sep 2020
- 2 Minutes to read
Why Monitor Service Bus Topics?
Service Bus Topics in a Business Orchestration connect Publishers and Subscribers. Their role is significant in keeping the business on. This also necessitates monitoring these Topics and the Topic Subscriptions.
When a Service Bus Topic is associated with a Serverless360 Composite Application, it is possible to monitor Service Bus Topic and Topic Subscriptions in various perspectives using the monitors in Serverless360.
Monitor Service Bus Topic and its Subscriptions on their Status
If the intention is to monitor the status, say the business demands the Topic to be always active, Serverless360 can monitor Topic and its Subscriptions status. By associating a Topic to Status Monitor or Threshold Monitor, it is possible to monitor their status, compare against the expected set and alert through configured notification channels
Monitor Service Bus Topic and its Subscriptions on their Properties
It is also possible to monitor the Topic on its Size in Bytes.
Topic subscriptions can be monitored on their properties below:
- Scheduled Message Count
- Active Message Count
- Dead Letter Message Count
- Transfer Message Count
- Transfer Dead Letter Message Count
Service Bus Topic monitoring with appropriate warning and threshold values can be set as in figure below. Monitoring on properties of Topic subscriptions is a distinct capability offered only by Serverless360. Please refer extensive documentation on Status Monitor and Threshold Monitor to choose the right monitor to meet your business need.
Bulk Monitoring for Service Bus Topic Subscriptions
Considering Service Bus Topics with good number of Subscriptions, configuring monitoring on their properties for every Topic Subscriptions would be a tedious process. Understanding the pain point Serverless360 has not got bulk monitoring configuration for Service Bus Topic Subscriptions. Below is the illustration on defining bulk monitoring configuration for several subscriptions in a Service Bus Topic.
Monitor Service Bus Topic on its Metrics
If the intention is to understand the message flow, reliability of the Service Bus Topic then the choice should be a Serverless360 Data Monitor. Data Monitoring can be configured for a Service Bus Topic on an extensive set of metrics. Service Bus Topic data monitoring with appropriate warning and threshold values can be set as in figure below
Data Monitoring documentation can provide more information.
Data Monitoring Recommendations
The table below lists down the combination of metrics to monitor the Service Bus Topic in various perspectives using Serverless360 Data Monitor.
|Monitoring Purpose||Metrics to Choose|
|Check if the Service Bus Topic is available||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 Topic 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 Topic size||Size (Bytes)|
Data Monitor can be configured with appropriate combination of metrics to meet various monitoring requirements.