As mentioned in the Introduction to Alarms section, you can create two types of monitoring (alarms) in BizTalk360 Cloud — Regular and Threshold alarms. Regular alarms can be set to provide periodic updates about the health of the BizTalk environment. They can be set in a recursive manner to occur specific day(s)/time(s) of your choice. In contrast, you may want to monitor the environment constantly and get alerted when things go wrong (ex: receive location gets disabled). This can be achieved using BizTalk360 Cloud threshold based monitoring.

Threshold alarms in BizTalk360 Cloud can be set to send immediate (or based on configurable persist duration) alerts when a threshold condition is violated in the environment. If required you can configure to monitor threshold violation only during specific time periods on days (say, weekdays between 0900 and 1700), which is useful if you wanted to monitor only during business hours. For instance, receive locations, send ports, orchestrations, and host instances are the heart of any BizTalk solutions. You can set a threshold value for the receive location(say, alert if the violation persists for more than 2 minutes). When the violation persists above the threshold value, BizTalk360 Cloud will immediately trigger an alert email saying that the violation persists more than 2 minutes in the receive location. BizTalk360 Cloud can also be configured to notify you when the situation becomes normal. You can also limit the number of alerts that will be sent (otherwise you may end up in infinite number of alerts being received for the same issue).

When you add a new environment to your BizTalk360 Cloud account, the environment will be created along with a demo alarm, if you have enough free artifacts on your plan.

We have introduced the concept of Demo Alarm to give you a feel of how the UI will look when you actually create an alarm and configure the monitoring for the environment. The demo alarm will be configured with up to 4 artifacts (receive location, orchestration, send ports, and host instances) from any of the applications in your environment. The demo alarm can be reconfigured or deleted as per your requirement.

The count of artifacts that are mapped in the demo alarm will be automatically deducted from the count (of artifacts) offered by your subscription plan. For ex., if you are on a Free plan (10 artifacts), the 4 artifacts mapped to the demo alarm will be deducted from the count of 10 and you will only have 6 artifacts remaining that can be mapped further.

Setting Up Threshold Based Monitoring

You can set up threshold based monitoring while creating alarms. You need to follow the steps below to set up threshold based monitoring:

  1. Follow the steps 1–4 as mentioned in Creating an alarm section

  2. Click 'New Alarm' in the Manage Alarms screen and select Threshold Monitoring

  3. Enter the Alarm name (ex:Threshold Monitor), enter a valid Email address (you can enter multiple email address as comma separated values), and Alarm Description. Click Next to move to next screen to set up alert on threshold violations

    By default, the logged in user id will be entered in the Email Id column. The user can enter multiple email address as comma separated values to receive separate alerts to all email address.

  4. Toggle on 'Alert on threshold violation' option. If you do not turn on, you will not be able to make any threshold violation settings

  5. Violation Persist Duration— You can set the duration after which you want to receive the notifications when there is a violation. For instance, you must receive notifications if the violation persists for 10 minutes. This avoids sending notifications too quickly as the violations may quickly resolve and return back to the normal state
  6. Limit number of alerts per violation — You can set the number of alerts you wish to receive per violation, say, 10 alerts per violation every 10 minutes. This will avoid getting infinite number of notifications and annoying the users
  7. Notification when situation becomes normal — You can change the setting to be notified when the situation becomes normal
  8. Set specific days and time to restrict the threshold violation alerts
  9. Click OK to save the alarm information

  10. The alarm will be created in the Manage Alarms page

You will receive the notification email once there is a violation in the state of any of the components in the server environment. The notification email will be something in the following format: