ServiceBus360 allows you to seamlessly monitor various things in your Event Hubs like the expected state of the Event Hub and other partition level parameters.

In this section, we will see how to set up monitoring on the Event Hub at the partition level. Partitions are one of the key differentiation in the way that the data is stored and retrieved compared to other Service Bus technologies like Queue and Topics. The traditional Queue and Topics are designed based on the “Competing Consumer” pattern in which each consumer attempts to read from the same queue, whereas Event hubs are designed based on “Partitioned consumer pattern”. The single lane queue model will ultimately result in scale limits, hence event hubs use partitioned consumer pattern to achieve the massive scale required.

It's important to make sure the partitions are healthy and running in an expected state to avoid any downtime sending messages to external systems. ServiceBus360 assists administrators by monitoring the Event Hubs against an expected status. For instance, you want to monitor the Event Hubs and want to be alerted when the status is not Active, you can easily set up monitoring for this by setting the expected state to Active. By doing this, the system will trigger an alert as soon as the send port status is not Active.

One of the important features of ServiceBus360 monitoring is, it allows you to set up monitoring for any desired state, not necessarily just healthy running state always. Most of the monitoring solutions will only monitor for a healthy state. When it comes to Service Bus, it's fairly normal; for example, you have some Event Hubs in not necessarily just healthy running state always. Most of the monitoring solutions will only monitor for a healthy state. When it comes to Service Bus, it's fairly normal; for example, you have some Event Hubs in SendDisabled state for some reason and you do not want someone to accidentally start it. If you wanted to achieve this in general purpose monitoring solutions, it may involve a considerable amount of custom development, whereas in ServiceBus360 it's out-of-the-box. 

When you are configuring monitoring for Event Hubs, once you select the Event Hub, you can then select one of the expected states from the drop down. 

  • Active
  • Disabled 
  • SendDisabled 
  • ReceiveDisabled 

To configure monitoring, the user must create alarms and then associate Event Hubs to the alarms.

Create an alarm:

  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 ‘Event Hub’.
  2. Click Alarms from the menu on the left
  3. Click the Add Alarm button to open the Add Alarm blade
  4. Enter Alarm Name
  5. Enter a summary for the alarm (This is optional)
  6. Click the Next button to navigate to the ‘Threshold Violations’ page
  7. Click ‘Alert on threshold violation’ to turn on the feature. You can configure alerts for threshold violations in this section.
  8. Click the Next button to navigate to the ‘Health Monitoring’ page
  9. Click ‘Enable Health Monitoring’ to turn on the feature. Enabling health monitoring allows users to get regular alerts on the status of the resource.
  10. Click Next to navigate to the ‘Notifications Channels’ page. By default, a notification email is sent from ServiceBus360 to the registered email ID (customizable) when the alarm is triggered due to a violation. You can also configure additional notification channels.
  11. Click the Save button to create the alarm

Associate the newly created alarm to an  Event Hub

  1. Click Event Hubs from the menu on the left menu
  2. Click the Monitoring icon on the right for the Event Hubs you want to associate the alarm
  3. The Select Alarm dropdown on the top left lists all the configured alarms. Select the alarm you want to associate with this Event Hub from the dropdown
  4. Click the Monitor Partitions button to open the Event Hub Partitions blade
  5. Select the parameters that you wish to monitor. You can choose to monitor parameters like Incoming Bytes Per Second, Outgoing Bytes Per Second, and Size In Bytes.
  6. Click Add to Monitor button to add the selected parameters to the alarm
  7. Click the Edit button to change the threshold values. Using this option, you can set the warning and error threshold values to the respective parameters.
  8. Click Save when done. Click the "Do not Monitor" button to remove the monitoring configurations for the entity from the particular alarm.