In this article, we will take a detailed look at the Azure Logic Apps section in BizTalk360 and the different components available in this section. In order to be able to monitor Logic Apps BizTalk360 needs to be granted permissions to access the Azure subscription. To achieve this, please follow the steps mentioned in this article. Once you have added the Azure subscription details in BizTalk360, you will be able to see the list of Logic Apps under your subscription. 

Follow the steps as shown below to view the list of Logic Apps under your subscription:

  1. Log in to BizTalk360
  2. Click Monitoring on the top of the left navigation menu
  3. Expand Manage Mapping and select Azure Services
  4. If there are no Azure subscriptions mapped to your environment, you will see a warning message as "No Azure Subscriptions Found/Enabled". Click "Go to Settings to Add/Enable". Refer this article to know the details of adding a new Azure subscription.
  5. If there is an active Azure subscription available, you will see the screen as shown below. Select Logic Apps tab -
    1. Select Alarm - This is the first step to be performed in BizTalk360 when you are setting up monitoring. Please refer this article to create a new alarm in BizTalk360. You can choose the alarm from the drop down to configure Logic apps for monitoring.
    2. Azure Subscription - You can choose the subscription from the drop down. Depending on the chosen subscription, the associated Logic apps will be listed in the below grid.
    3. Logic Apps Details - The grid will display the information about the Logic apps under the selected subscription. You can get the details such as the Logic App name, the endpoint URL, Auto correct status (Enabled/Disabled) and the number of retries, the expected status, the current status, and the last run time.
    4. Expected State - Select the Logic app that you wish to monitor (by selecting the check box) and select the Expected State drop down. You can monitor a Logic app against the following states - Enabled, Disabled, Do Not Monitor. Setting the Expected state field will start monitoring the Logic app and will be compared with the current state of the Logic app. If the expected state matches the current status, the monitoring status will display as Healthy (Green color) against the Logic Apps tab.
    5. Auto Correct - You can choose to automatically correct the status of the Logic App to the expected state if the current state does not match the expected state. The BizTalk360 monitoring service will take the responsibility of setting the Logic App to the expected state (as defined).
      The auto correct drop down will not get activated unless you perform activity in Step 4 (Setting the expected state)
    6. Enabling Auto Correct - Select the check box against the artifact and Enable Auto Correct from the drop down. You will notice Auto Correct gets enabled with a Max Retry count of 5 (default) and Attempt count of 0.
      • Max Retries - Click the numeric value to set the number of retries the monitoring service should attempt
      • Attempt - Shows the number of times the monitoring service has performed the retry operation
    7. Remove Orphaned - This button will be enabled only when a Logic app, that is configured for monitoring within BizTalk360, is removed from the Azure Portal. In this case, you can select the Logic app and remove it.
    8. Refresh - Click the Refresh icon to refresh the Logic apps information. When you click Refresh, BizTalk360 monitoring service will actually fetch the information of the Logic app from the Azure portal.

logic apps monitoring screen in biztalk360