Azure Service Bus Resource

Azure Service Bus is an asynchronous and distributed messaging service offered by Microsoft Azure. It provides publish and subscribe capabilities, queues, and commit messages to facilitate communication between distributed applications and components. Service Bus allows producers to send messages to topics or place messages on queues, while consumers subscribe to topics or retrieve messages from queues for processing. It ensures reliable delivery of messages even in case of temporary failures and offers advanced features such as message filtering, rate control, and expiration time-based message queuing. Additionally, Azure Service Bus integrates seamlessly with other Azure services such as Azure Functions, Logic Apps, and Azure Functions. It is widely used in distributed architectures, microservices, real-time applications, event systems, and application integration scenarios, providing a reliable and scalable solution for exchanging messages between components of a system in the Azure cloud.

How to monitor Service Bus on One Platform

1 – In the side menu, click on Services Hub


2 – In the Queue category, click on the  Service Bus (Azure) card


3 – You will be directed to the Service Bus (Azure) configuration form, fill in the fields


4 – If you want, you can configure automatic incident opening. In the Open automatic incident section, fill in the fields:

  • Severity -> Choose between “SEV-1 – Critical”, “SEV-2 – High”, “SEV-3 – Moderate”, “SEV-4 – Low”, “SEV-5 – Informational” or “Not Classified”;
  • Check Interval in seconds -> This is the interval at which checking will take place (this interval cannot be less than the number of failures x the Interval configured in the monitoring form;
  • Failures to open automatic incident -> It is the number of failures necessary to open the automatic incident;
  • Check Interval in seconds -> This is the interval in which checking will take place (this interval cannot be less than the number of hits x the Interval configured in the monitoring form;
  • Hits to close automatic incident -> It is the number of hits needed to close the automatic incident;
  • Responders -> These are the teams that will be notified if there are incidents in this monitoring, and you can add one or multiple teams;

If necessary, you can create a team by clicking + RESPONDER, you will be directed to the form

to create the team, then click on the button  for the new team to appear in the list

***Don’t forget to activate the Enable to set up automatic incidents opening toggle to save the automatic incident opening settings


5 – Click on CREATE MONITORING 

Azure Service Bus is an asynchronous and distributed messaging service offered by Microsoft Azure. It provides publish and subscribe capabilities, queues, and commit messages to facilitate communication between distributed applications and components. Service Bus allows producers to send messages to topics or place messages on queues, while consumers subscribe to topics or retrieve messages from queues for processing. It ensures reliable delivery of messages even in case of temporary failures and offers advanced features such as message filtering, rate control, and expiration time-based message queuing. Additionally, Azure Service Bus integrates seamlessly with other Azure services such as Azure Functions, Logic Apps, and Azure Functions. It is widely used in distributed architectures, microservices, real-time applications, event systems, and application integration scenarios, providing a reliable and scalable solution for exchanging messages between components of a system in the Azure cloud.

How to monitor Service Bus on One Platform

1 – In the side menu, click on Services Hub


2 – In the Queue category, click on the  Service Bus (Azure) card


3 – You will be directed to the Service Bus (Azure) configuration form, fill in the fields


4 – If you want, you can configure automatic incident opening. In the Open automatic incident section, fill in the fields:

  • Severity -> Choose between “SEV-1 – Critical”, “SEV-2 – High”, “SEV-3 – Moderate”, “SEV-4 – Low”, “SEV-5 – Informational” or “Not Classified”;
  • Check Interval in seconds -> This is the interval at which checking will take place (this interval cannot be less than the number of failures x the Interval configured in the monitoring form;
  • Failures to open automatic incident -> It is the number of failures necessary to open the automatic incident;
  • Check Interval in seconds -> This is the interval in which checking will take place (this interval cannot be less than the number of hits x the Interval configured in the monitoring form;
  • Hits to close automatic incident -> It is the number of hits needed to close the automatic incident;
  • Responders -> These are the teams that will be notified if there are incidents in this monitoring, and you can add one or multiple teams;

If necessary, you can create a team by clicking + RESPONDER, you will be directed to the form

to create the team, then click on the button  for the new team to appear in the list

***Don’t forget to activate the Enable to set up automatic incidents opening toggle to save the automatic incident opening settings


5 – Click on CREATE MONITORING