Standard logic app

Logic Apps Standard can be leveraged across various business scenarios to automate processes, integrate systems, and streamline workflows.

Imagine you're managing a complex system that relies heavily on Logic Apps to automate various processes. Ensuring these Logic Apps are running smoothly is crucial for your business operations. With state monitoring in BizTalk360, you might expect a Logic App to be always enabled. Let's say if a Logic App becomes disabled due to payment issues, compliance concerns, or similar issues, you receive immediate notifications to address the situation promptly.

When you set the expected state, the Logic App will be automatically monitored. The BizTalk360 monitoring service periodically checks the current state, comparing it with the expected state. If they match, the health status is marked as "Healthy" (highlighted in green); if they differ, it's marked as "Error" (highlighted in red).

Logic app standard monitoring via BizTalk360

You can execute the following steps to set up an alert for Azure Logic Apps:

Log in to the BizTalk360 application.
Navigate to Monitoring -> Manage Mapping -> Azure Services -> Logic apps in the selected environment.
Select the Subscription and any associated logic app to set up monitoring.
Choose the Alarm (refer Manage Alarms) for which you would like to associate the alerts.
Set the value of the 'Expected State' against the logic app.

Rule based monitoring:

You can configure the rules with condition-based filter to monitor with standard logic app with the metric.

Say for example, The number of workflow action completed directly reflects the reliability of your standard logic app workflows. When you want to be notified when the count of Workflow action completed is less than 25. The monitoring will be started for this rule and sends alert if the condition becomes true.

Follow the below steps to configure the monitoring metrics,

Click on the Subscriptions which lists the available logic app along with their current state, expected state.
Click on the logic app, which opens the configuration blade, where you can configure the monitoring rule.
Set the Aggregation period which can be minimum of 10 minutes to maximum of 24 hours (The process of taking multiple input values and then using them to produce single output value)
Configure threshold rules with the below metrics,
- Connections
- Average memory working set.
- Data in
- Data Out
- Function execution count
- Response time
- Memory working set.
- Requests
- Workflow action completed count.
- Workflow runs completed count.
- Workflow runs started count.
- Workflow runs dispatched count.
- Workflow triggers completed count.
- Workflow job execution delay
- Workflow job execution duration
- Workflow triggers failure rate
- Workflow actions failure rate
- Workflow runs failure rate.
- Logic App job pull rate per second.

Auto correct

To automatically correct the state of the Logic App Standard, select the Logic App and click on the 'Auto Correct' option. From the dropdown menu, choose 'Enable'. If the current status of the Logic App Standard switches to "Disabled" (contrary to the expected status) at any point , monitoring service will then attempt to automatically enable the Logic App Standard, adhering to the specified number of retry attempts set in the Max Retry section.

Monitoring Dashboard

The monitoring dashboard will reflect the health of the logic apps.

Alerts

In order to receive email notifications from BizTalk360 on the threshold violation alerts (and auto-correction 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 Logic App with the auto-correction details (as shown in the email below)

How to Remove Orphaned Logic App Standards?

If you happen to rename or delete the Logic Apps being monitored within an alarm, they will become Orphaned. Consequently, they will appear as "Orphaned" in the User Interface, and their status will be marked as unhealthy.