When to choose a Status Monitor?
Consider a Business solution orchestrated using Azure Serverless components like Service Bus Queues, Logic Apps and Function Apps. The monitoring requirement here is to get a status update on all the entities at every one hour interval. The status report should be shared with the team members through the Slack notification channel. To meet this requirement, what Serverless360 offers is a status monitor.
Configuring a Status Monitor
Configuring a Threshold monitor in Serverless360 involves the following steps.
Create/ Edit a Status Monitor, in every Composite Application created, by default a status monitor will be present. However you can create as many number of status monitors as per your requirement.
Define the Status Monitor, edit the status monitor configuration to define frequency at which the status report should be generated and shared.
Define the Notification Channels, for the status monitor to share the alerts. Turn on those notification channels from the list of configured channels through which this status monitor is ecpected to send alert on Below is an illustration that can serve as a guide to configure a threshold monitor.
Associate Entities, multiple entities can be associated to a single status monitor. Serverless360 has capabilities to monitor the following Azure entities on their state, metric/ properties in a status monitor
- Service Bus Queues/ Topics/ Topic subscriptions
- Event Hubs
- Logic Apps
- Function Apps
- Storage Queues/ Blobs/ Files
- API Endpoint
Configure threshold values on enitity properties , Serverless360 permits defining an expected state against current state of the associated entities. It is possible to monitor the entities on the value of their properties and metrics. In this case, the warning threshold and error threshold can be configured to generate an appropriate warning or error monitoring status. Below is an illustration that can serve as a guide to configure warning and error threshold values on metrics or properties of the associated entities.