Alarms Management

Serverless360 understands the problems faced by enterprises and offers an out-of-the-box monitoring solution that assists administrators to monitor the distributed Azure Services grouped in an integration solution. With Serverless360, it is easy for you to configure alarms for various metrics and get notified in case of violations and take necessary corrective actions. An enterprise integration solution may contain multiple Azure services being used, these resources from various subscriptions can be grouped together to make a more meaningful monitoring.

Types of Alarm

In Serverless360, you can configure 3 main types of alarm:

1. Threshold violation alarms - used when a condition is violated, for example: a disabled receive location
2. Health Check Notification alarms - used for Health/Status check
3. Data Monitoring alarms - used to set up Data monitoring alerts

Threshold Violation Alarms

Threshold alarms in Serverless360 can be set to send immediate (or based on configurable persist duration) alerts when a threshold condition is violated on the resource. If required, you can configure to monitor threshold violation only during specific times on days (say, weekdays between 0900 and 1800), which is useful if you wanted to monitor only during business hours. You can also limit the number of alerts that will be sent (otherwise you may end up in indefinite number of alerts being received for the same issue).

Health Check Alarms

It's one of the common practice in any integration solution for the support people to maintain daily/weekly routine to take a look at the overall health status of the integration solution(s). Serverless360 helps to automate that process by creating a daily health check/status alarm at set timing (ex: Mon-Fri, 11 AM). When you are creating a "Health Monitoring Alert", you can set up the alarm to monitor the health of the integration solution on a periodic basis. You can configure the days/times as per your convenience/requirement.

Data Monitoring

How many times in a day does your support person have to watch for ‘Trigger Runs Succeeded’ in a particular Logic App and take an appropriate action, or look out for ‘Total Billable Executions’? We understood that it would be nice if there was a way to set up monitoring on a set of metrics and get notified when the entity doesn’t perform based on Business SLA? Yes, that’s exactly what Serverless360 achieves through the concept of data monitoring.

Creating an Alarm

Monitoring can be setup in less than 5 minutes. You need to take the following steps:

1. Create an alarm – Provide basic settings like name, alarm summary, type of alarm and the alarm configurations.

2. Add mappings to the alarm – Map the Azure resources that you want to monitor in the composite application

3. Set Threshold values – Edit the threshold values that you expect for the every metrics