View the earlier version. Version 7.10

As mentioned in the Introduction to Alarms section, you can create three types of monitoring (alarms) in BizTalk360 — Regular, Threshold, and process monitoring 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 wanted to monitor the environment constantly and get alerted when things goes wrong (ex: receive location gets disabled). This can be achieved using BizTalk360 threshold based monitoring. Process monitoring alarms can be created and mapped to process monitors to monitor the state of a specific receive location and/or send port during a particular point of time (say specific hour in the day or once in every 15 minutes and so on).


Threshold alarms in BizTalk360 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 a specific times on days (say, weekdays between 0900 and 1700), which is useful if you wanted to monitor only during business hours. For instance, CPU and memory are the vital components of any server. You can set a threshold value for the CPU and memory (say, alert if free memory goes below 10%). When the CPU/memory goes below the threshold value, BizTalk360 will immediately trigger an alert message through your notification channels saying that the memory has gone below the threshold condition. BizTalk360 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 indefinite number of alerts being received for the same issue). 


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–6 as mentioned in Creating an alarm section

  2. Turn on 'Alert on threshold violation' option. If you do not turn on, you will not be able to make any threshold violation settings
  3. 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
  4. Limit 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 indefinite number of notifications and annoying the users
  5. Notification when situation becomes normal — You can make the setting to be notified when the situation becomes normal
  6. Set specific days and time to restrict the threshold violation alerts 
  7. Save the alarm information



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: