Service Bus (Azure)

The Azure Service Bus is an asynchronous and distributed messaging
service offered by Microsoft Azure. It provides features for
publish-subscribe, queues, and message confirmation to facilitate
communication between distributed applications and components. The
Service Bus allows producers to send messages to topics or place
messages in queues, while consumers can subscribe to topics or retrieve
messages from queues for processing. It ensures reliable message
delivery, even in case of transient failures, and offers advanced
features such as message filtering, rate control, and message queuing
based on expiration time. Additionally, Azure Service Bus seamlessly
integrates 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-driven
systems, and application integration scenarios, providing a reliable and
scalable solution for message exchange among components in the Azure
cloud.

To monitor Service Bus on the One Platform:

  1. Go to the product application where you want to add Service Bus as a dependency.
  2. Click on the “Products” menu and select the desired product card.
  3. Click on the name of the application you want to monitor.
  4. Scroll down to “External Dependencies,” located just below the latency graph.
  5. You can either add an existing dependency by searching for it in the
    search field, or you can add a new one by clicking the green button
    with a plus (+) symbol.

 

When you click on “Add,” a modal will appear. In this modal, you will
name your queue and choose the Environment. In the “Check type” field,
select the option “Queue,” and in the “Method” field, choose “Service
Bus (Azure).” After selecting the method, a field for “Healthcheck URL”
will appear.


 

Choose the type of monitoring, whether it’s Topic or Queue. Below is an example string for the Service Bus:

example:Endpoint=sb://namespace.servicebus.windows.net/;SharedAccessKeyName=keyname;SharedAccessKey=keyvalue

 

Note: For security reasons, it is not permitted to enter an IP in the
healthcheck field. To monitor an IP, you need to enter it in a secret
and use it in healthcheck

The Azure Service Bus is an asynchronous and distributed messaging
service offered by Microsoft Azure. It provides features for
publish-subscribe, queues, and message confirmation to facilitate
communication between distributed applications and components. The
Service Bus allows producers to send messages to topics or place
messages in queues, while consumers can subscribe to topics or retrieve
messages from queues for processing. It ensures reliable message
delivery, even in case of transient failures, and offers advanced
features such as message filtering, rate control, and message queuing
based on expiration time. Additionally, Azure Service Bus seamlessly
integrates 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-driven
systems, and application integration scenarios, providing a reliable and
scalable solution for message exchange among components in the Azure
cloud.

To monitor Service Bus on the One Platform:

  1. Go to the product application where you want to add Service Bus as a dependency.
  2. Click on the “Products” menu and select the desired product card.
  3. Click on the name of the application you want to monitor.
  4. Scroll down to “External Dependencies,” located just below the latency graph.
  5. You can either add an existing dependency by searching for it in the
    search field, or you can add a new one by clicking the green button
    with a plus (+) symbol.

 

When you click on “Add,” a modal will appear. In this modal, you will
name your queue and choose the Environment. In the “Check type” field,
select the option “Queue,” and in the “Method” field, choose “Service
Bus (Azure).” After selecting the method, a field for “Healthcheck URL”
will appear.


 

Choose the type of monitoring, whether it’s Topic or Queue. Below is an example string for the Service Bus:

example:Endpoint=sb://namespace.servicebus.windows.net/;SharedAccessKeyName=keyname;SharedAccessKey=keyvalue

 

Note: For security reasons, it is not permitted to enter an IP in the
healthcheck field. To monitor an IP, you need to enter it in a secret
and use it in healthcheck