Azure Logic Apps

In this section, the following is discussed:

• User Access Policy Settings For Logic Apps Data Monitoring
• Setting up a Logic Apps Data Monitor

User Access Policy Settings For Logic Apps Data Monitoring

In this article, we will explain the different user access policy settings for Azure Services. Only Super Users will have the permissions to add or remove an Azure subscription in BizTalk360. For detailed steps on adding an Azure subscription to BizTalk360, please refer this article. For Normal users, in order to be able to access the Azure Services section and set up data monitoring on Logic Apps, super users need to grant the permissions under the User Access Policy section in BizTalk360 Settings.

Let's say Scott is a Normal User at ACME corp, and he has to be given permissions to access the Azure Services section within BizTalk360. 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 right corner of the window

• Select User Access Policy from the left navigation menu. Create a new user by clicking the New button

• Enter the user name as Scott, 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. Click Next
• In the User Access (module wise) section, enable the toggle for Monitoring section. This will open up the options available under the monitoring section. Select the Data Monitoring and 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 check boxes.

• Click OK to save the user permissions
• The user will get saved within BizTalk360, and the normal user will be able to access the Azure Services section

Setting up a Logic Apps Data Monitor

Follow the steps as shown below to create an Logic Apps Data Monitoring alarm:

• In case you did not do it earlier, follow the steps as mentioned in this section to create a Data Monitoring alarm
• Select the 'Use this alarm for Data Monitor Alerts' check box to map the current alarm to Data Monitors. Only when this option is selected, the 'Notify on Success as well' check box gets activated.
• The 'Notify on Success as well' check box is optional for Data Monitoring, while the Use this alarm for Data Monitor Alerts option is mandatory
• Click OK to save the alarm information
• Choose Alarm - As mentioned above, the first step is to setup Logic Apps data monitoring is to create an alarm. Once you have created the alarm, the alarm name will be displayed in the dropdown. Select the alarm that should be used for Logic Apps data monitoring purposes.
• Friendly Monitor Name – A meaningful name for Logic Apps Data Monitor. Say, as per your requirement you want to get notified with a warning message when the number of Billable Executions is greater than 25 in specific Logic App and throw an error message when the number of Billable Executions is 50. The monitor can be set as “Latency Monitor in LogicApps LogicAppName > 25, trigger warning;> 50, trigger error”

• Azure Subscription – Select the subscription name from the list of Azure subscription that has been configured for the environment in the settings section
• Resource Group – Select the Resource Group which contains the Logic App you want to monitor, from the list of Resource Groups which are available in the selected subscription
• Logic App – Select the Logic App that you want to monitor from the list of Logic Apps that’s available in the selected subscription
• Metric – Select metric that you want to monitor from this dropdown

• Warning Threshold – Select the value from the drop down on when you want to be notified when there is a warning. The first drop down is to select the Operator (>, <, =) and the second operator is to select the warning value. For e.g. When Billable Action Executions > 25, throw a warning
• Error Threshold – Select the value from the drop down on when you want to be notified where there is an error. The first drop down is to select the operator (>, <, =) and the second operator is to select the warning value. For e.g. when Billable Action Executions > 50, throw an error Note: For the metrics related to Latency the unit of the Error/Warning threshold will be time (ms). So Run Latency > 25 means Run Latency > 25 milliseconds

• How often you want to monitor – Select the duration how often you want to monitor for Logic Apps metrics. The options are Daily, Weekly and Monthly. Depending on the selection, you can add further filter criteria on how often you want to monitor
  • Daily – Will set up the data monitor to execute daily
  • Weekly – The data monitor will execute on the selected days of the week (Everyday, Monday-Friday, or the selected day of choice). To add a single day of the week, click the control and select the day of your choice
  • Monthly – The data monitor will execute on the selected day of the month. To add specific day of the month, enter the date in the space provided or select the date from the dropdown Note: If a day is not present in the month (say, 29th Feb), then system will skip that month and generate the results on the specified day in the month
• When during a day – Select the time when the data monitor must execute on a day during the business hours. You can customize your business hours by selecting the values from the Business Day Start and Business Day End option Note: By default, the business day start time is 9 AM and business day end time is 5 PM.
• At what time – Select the time when the data monitor should execute on a day. The options are – At the end of the business day and at a set frequency (every 1 hour or 15 minutes)
• At the end of the business day – If this option is chosen, the data monitor will execute depending on the value chosen in the Business Day End Field. For e.g. if the business end time specified is 5 PM (default value), the data monitor will execute exactly at 5 PM
• Monitor every X minutes/hours – You can define specific intervals during the business hours when the data monitor should execute. The options available are Minutes and Hours
• Minutes – Select the number of minutes after which the data monitor should execute. E.g. 2 hours means the data monitor will execute once in every 30 minutes Note: The minimum time interval supported is 15 minutes, which means the data monitor will execute 4 times (15 minutes x 4 = 60 minutes) in an hour
• Hours – Select the number of hours after which the data monitor should execute during the business hours. E.g. 2 hours means the data monitor will execute once in 2 hours between 9 AM and 5 PM Note: The minimum time interval supported is 1 hour.
• Advanced – This section can be used to define advanced settings for data monitoring. You can define a date range (from date and to date) when you want the data monitor to execute. You can set up a data monitor to start, say on a Monday and end on the next Thursday. In addition to this, you can set up the settings mentioned above in the previous steps. This means the data monitor will only start to run next Monday and will not execute after Tuesday Note: By default, the advanced section will be in collapsed state. Click the ‘>’ button to expand the advanced section and make the settings.

• How do you want to check?
  • Based on only query result count (no date/time filter) – Selecting this option will execute the query based on the setting for trigger time (Defined under ‘At what time’ as explained above in step 10). Say, the monitor at the set frequency is set to every 15 minutes, the query execution will happen once in every 15 minutes till the specified end time.
  • Based on query result with date/time range – Selecting this option will activate the "Choose date/time column" drop down from where the appropriate option can be selected (Interchange Time). When selected, the query will be constructed with the from/to date time filter based on the selected date/time column, and execute the query with the time range. Say, for instance, if the data monitor is scheduled to execute every hour from 9 AM to 6 PM, and currently the time is 11:59 AM, during the next run of the data monitor at 12 PM, it will look for the query results between 11:01 AM and 11:59 AM and generate the results.
• Summary – The summary information will automatically be populated based on the information selected in the previous columns
• Save & Close – Once all the values are selected in the previous steps. Click Save & Close to save the settings.
• Save & Add another – The entered values will be saved and a new screen will be displayed to create another data monitor
• Close – Click close to discard the changes. When the close button is clicked, the system will display a confirmation message as “There are unsaved change. Do you still want to close?”. Click Yes to close the Data Monitoring creation window. Click No to remain on the same page.