In this article:

  1. Introduction to Monitoring and Notification
  2. Getting started with Monitoring and Notification in ServiceBus360

Introduction to Monitoring and Notification

Azure Service Bus is a cloud-based messaging platform for connecting applications, services, and devices irrespective of their locations. Applications running on Azure, on-premise systems, or both, can communicate with each other, and numerous applications can be accessed with minimum response time. With ServiceBus360, monitoring Azure Service Bus becomes a lot easier. ServiceBus360 is a simple platform to manage your Azure Service Bus namespaces. It provides efficient operations capabilities on any Service Bus resource like Queues, Topics, Relays and Event Hubs. With ServiceBus360 it is easy to configure alarms for various metrics and get notified in case of violations and take necessary corrective actions. An enterprise messaging solution may contain multiple Service Bus resources being used. These resources from various categories can be grouped together to make more meaningful monitoring.

eaqZM9KvloRcYQiL1l0dg1YT9E4yrEN8oQ.png

So what can ServiceBus360 Monitor?

ServiceBus360 allows you to set alerts and monitor the Namespaces at resources level such as:

  • Queues
  • Topics
  • Relays
  • Event Hubs

What are the notification channels available?

In the current version, ServiceBus360 comes with:

  1. PagerDuty
  2. SMTP
  3. Slack
  4. Microsoft Teams
  5. WebHook
  6. Operation Management Suite (OMS)

Getting started with Monitoring and Notification in ServiceBus360

Setting up monitoring and notification in ServiceBus360 is a simple process. As a getting started guide, let's take a look at a simple scenario. ACME Corporation wanted to monitor all the Queues in the Namespace 'Dev-Messaging'. Setting up monitoring and notification in ServiceBus360 for this scenario is a two step process

  • Create an alarm and specify the threshold levels at which the alert should be triggered.
  • Associate the Queues in the Namespace 'Dev-Messaging' to the threshold alarm to set up monitoring

Creating An Alarm

To create an alarm in ServiceBus360, you need to follow the steps as shown below: 

  1. From the Home Dashboard, click Manage Namespace button of a namespace for which you want to create the alarm. The namespace should be of type ‘Messaging’.
  2. Click Alarms from the menu on the left
  3. Click the Add Alarm button to open the Add Alarm blade
  4. Enter the Alarm name (ex: Queue Monitoring), enter a valid Email address (you can enter multiple email address as comma separated values), and Alarm Description (Optional). Click Next to move to next screen to set up alert on threshold violations
    The user 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 a single alert to all email address in one go.
  5. Click Next to move to next screen to set up alert on threshold violations
  6. Select the 'Alert on threshold violation' toggle on/off and set persist duration, the number of alerts per violation, and date & time. Click OK.
  7. Click Next to enter the Health Monitoring Alert page  
  8. In this page, toggle on the Enable Health Monitoring button
  9. Choose the days and times you want to receive a periodic update about the health of your Service Bus Namespace Resources. Click Next 
  10. In the Notification Channel blade, select the channel(s) that you wish to receive the notifications from ServiceBus360. To configure custom notification channels read this section.
    By default, Email notification channel will be enabled in ServiceBus360.
  11. Click Save to create the alarm


Associate Resources to Alarm

Once you have created an alarm, you can associate the Namespace Resources (Queues, Topics, Relays, and Event Hubs) with the alarm. Once you associate the resources with the alarm and set the threshold values, ServiceBus360 will start monitoring the status of the properties/metrics based on the threshold condition. If there is any threshold violation, you will receive the alert notification after the persist duration is elapsed (we set 2 minutes in this example when we created the alarm).

To set up monitoring on the Queues, select the Queue ('Orders' in this example case) that you wish to monitor, and click on 'Monitoring' icon against the Queue name. You can set up monitoring of the Queue at any particular state. For instance, if you want the expected state of the Queue to be 'Enabled', ServiceBus360 will monitor the status of 'Queue'. Whenever the status turns to Disabled, ServiceBus360 will immediately notify through an alert. You can repeat the same process for other Resources.