- 16 Feb 2023
- 3 Minutes to read
- Updated on 16 Feb 2023
- 3 Minutes to read
In this article, we will take a detailed look at the end-to-end working scenario of setting up an Azure Service Bus Queue monitoring with a real-time scenario. The following will be discussed:
- An end-to-end scenario of monitoring Azure Service Bus queue
- How to assign permission for the user(s) to manage Azure Service Bus Queues
Setting up monitoring Azure Service Bus Queues
- Select the 'Azure Service Bus' Queues tab.
Enter the following fields:
NameSpace ConnectionString - Connectionstring of the namespace which contains the Service Bus Queue which needs to be monitored
Queue Name - The name of the Service Bus Queue which needs to be monitored
Configure the conditions for threshold alerts under 'Monitoring Rules'
To get the NameSpace ConnectionString and Queue Name, go to the 'Azure Management portal' and copy the information below
- Click 'Save' to create monitoring for the Queue
- The monitoring dashboard will reflect the health of the Queue
- In order to receive email notifications from BizTalk360 on the threshold violation alerts, you need to configure the 'SMTP settings' under 'BizTalk360 Settings'. Follow the steps in this article to be able to configure the SMTP settings in BizTalk360. You will receive an email notification with the exact details of the status of the Azure Service Bus Queues
How to assign permissions to manage Azure Service Bus Queues
By default, only Super Users have permissions to grant access to set up monitoring in BizTalk360. For Normal users, in order to be able to access the queues section and set up monitoring on Azure Service Bus Queues, a super user needs to grant the permissions in the 'User Access Policy' section in BizTalk360 Settings.
Follow the steps as shown below to grant access permissions to a normal user:
- Log in to BizTalk360 (as a Super User)
- Click the 'Settings' icon at the top left corner of the window, which is right below the 'Home' icon.
- Select 'Team Management' from the left navigation menu. Create a new user by clicking the 'Add User' button
- Enter the user name, and domain name, and select the environment for which the user will have access (say, Testing/Staging/Non-Production). Click 'Next'
- Choose the 'Applications' for which the user will have permissions and click 'Next'
- In the 'User Access Profiles' section, enable the toggle for the 'Operation ' and the 'Monitoring ' section. This will open up the options available under the 'Operation' and 'Monitoring' section
- Under 'Operations', select the 'Azure Services' check box in order for the normal user to have access to Azure Services section. You can also select the other sections/features that the user will have access to by selecting the checkboxes
- Under 'Monitoring', select at least 'Manage Alarm'
- Click 'OK' to save the user permissions
- The user will get saved within BizTalk360
What is new in v10.5?
- Service Bus Queue Monitoring is moved under Azure Service (Monitoring->Manage Mapping->Azure Service).
- Service Bus Queue can be monitored by adding their subscription. Whereas in previous versions users need to add the queues using the namespace to monitor.
After Migrating to v10.5, The Queues mapped for monitoring in previous versions will not be listed in the manage mapping sections, only in the dashboard you can see the queues that have been mapped for monitoring, but it does not have the current monitoring status. Follow the below steps to monitor the service Bus queues after the 10.5 upgrade,
1. Navigate to the Feature migration page in settings, you can see the migration status for ServiceBus Queue feature as failed
2. Follow this article to add Azure subscription to BizTalk360
3. Move to the Feature migration page and click the 'Retry Migration' option. Now the migration status of the service bus queue will become a success
4. Now on successful migration, the service bus queues available under the added subscription will get listed under Manage Mapping -> Azure Service. You can select the queues and configure threshold rules for monitoring.