In this article:

  1. Introduction to alarms in ServiceBus360  
  2. Setting up threshold monitoring in ServiceBus360
  3. Setting up health check notifications in ServiceBus360
  4. Additional alarm operations in ServiceBus360

Introduction to alarms in ServiceBus360

The first step in monitoring using ServiceBus360 is to create Alarms. Alarms in ServiceBus360 acts like a package to associate things together. Example: You may want to monitor resources in few Namespaces together. Alarms help you to achieve this objective. With ServiceBus360 you can create 2 types of alarms to monitor your Service Bus resources:

  • Threshold violation alarms (used when a condition is violated)
  • Health Check Notifications (used for Health/Status check)

Setting up threshold monitoring in ServiceBus360

The threshold alarm comes in handy, when you want to monitor a Namespace constantly and get alerted when things go wrong (ex: Queue size exceeds a set limit). Threshold alarms in ServiceBus360 can be set to send immediate (or based on configurable persist duration) alerts when a threshold condition is violated in the Namespace. If required you can configure to monitor threshold violation only during specific time periods on days (say, weekdays between 09:00 and 17:00), which is useful if you wanted to monitor only during business hours. For instance, you can set a threshold value for the Relay(say, alert if the violation persists for more than 2 minutes). When the violation persists above the threshold value, ServiceBus360 will immediately trigger an alert email saying that the violation persists more than 2 minutes in the Relay. ServiceBus360 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 receiving an unlimited number of alerts being received for the same issue).

Follow the steps below to set up threshold monitoring:


  1. From the Home Dashboard, click Manage Namespace button of a namespace for which you want to create the alarm.
  2. Click Alarms from the menu on the left navigation pane
  3. Click Add Alarm to open the Add Alarm blade

    vIQj9C-Ezz7hWfWt4jCHSBt2GcUJAV_FhA.png


  4. If you try to configure alarms more than your license plan the system will prompt a message as "Alarms limit reached! As per your license plan, you have already added X of X number of alarms".

    JjRjDauuSGR8CfF0KiPWHkwtZ-PZFWsIGA.png


  5. In the Add Alarm blade, enter a descriptive name for the Alarm, Alarm Description, and  recipient email id (you can enter multiple email ids as comma separated values).

    -2tnz8Rccoe_GtY6YI8ufXrYSHjvA0sMDQ.png


  6. The users can enter multiple email ids as comma separated values to receive separate alerts to all email id's or enter semi-colon separated email ids to receive single alert (email count) to all email address in one go.
  7. Click Next to enter the Threshold Alarm page


    qpDBuf6il_-M8omwpfOc-n5I-wQD8fwpkg.png


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

    g8Rl_wGbIjqsrPNoAceqYAyKI6plKVmpvA.png


  9. 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
  10. 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
  11. Notification when situation becomes normal — You can make the setting to be notified when the situation becomes normal

    ARFpOuOUxxvGtfwCWgdcR8_gFIsShUTz-Q.png


  12. Set specific days and time to restrict the threshold violation alerts
  13. Click Save to save the alarm information



Setting up health monitoring in ServiceBus360

It's one of the common practice in supporting Service Bus platform for support people to maintain the daily/weekly routine to take a look at the overall health status. ServiceBus360 helps to automate that process by creating a daily health check/status alarm at set timing (ex: Mon-Fri, 9 AM). When you are creating an alarm, on the "Health Monitoring Alert" page, you can set up the alarms to monitor the health of the Namespace Resources on a periodic basis. You can configure the days/times as per your convenience/requirement. To set up health check alarm:

  1. Follow the steps 1-7 as shown in the setting up threshold alarm section
  2. Click Next to enter the Threshold Alarm page. Turn off the 'Alert on threshold violation' option

    JShcIZRP86fieAc6i5-9uQKE0ZAR5wmTMA.png


  3. Click Next to enter the Health Monitoring Alert page
  4. In this page, toggle on the Enable Health Monitoring button

    4rhJ0DTd9gOVHY-V513RQE3V1wLrcBKxIQ.png


  5. Choose the days and times you want to receive periodic update about the health of your Service Bus Namespace Resources
  6. Click Next to create the alarm


    dGDTHPPuDU7-P9eOAHwRc53MGHp0QnheiQ.png


Additional Alarm operations in ServiceBus360


26YuWSx1mbIv2e1ZvRVl16crFSktjixqrw.png


  1. Add Alarm- Click this option to add a new threshold/health/consolidated alarm to the Namespace
  2. Reset- This option allows users to reset the notification alert limit set per violation
  3. Refresh - Click the refresh button to refresh the configured alarm information
  4. Edit- Click Edit to make changes to the configured alarms in the Namespace
  5. Delete- You can delete an alarm by clicking the Delete icon of the corresponding alarm. Once the alarm is deleted, the resources associated with the alarm will also be deleted. 
  6. Alarm Status - Displays the current status of the alarm