Logic App

Introduction

Logic App is a cloud service that helps users to schedule, automate, and orchestrate tasks, business processes, and workflows when they need to integrate apps, data, systems and services across enterprises or organizations.

Enable & Disable

Users can perform the following actions using Turbo360:

Enable or Disable a Logic App to reflect its status in the Azure Subscription.

Bulk Start / Stop operations can be performed using a single click in the Logic App resources section.

Run trigger

Turbo360 allows users to invoke the Logic App by sending a message to the trigger.

The Run trigger option allows users to modify a message and resubmit it to an endpoint, allowing their Logic App to be recovered from the error condition.

When a user enters a specific Logic App, the Run trigger option appears at the top to invoke the trigger. By providing the trigger details and sending the message, the triggering operation can be performed.

Run history

Run history produces the list of Logic App runs along with its start time, duration and tags. Clicking on the run identifier produces the run details of the Logic app run.

It is possible to drill down to every run action and trigger to understand the workflow execution along with the trigger inputs and outputs.

Optional Settings

Users can make use of the Optional Settings in the Run history tab to perform the following options.

Advanced Search

Logic App runs can be filtered using Advanced search by choosing the From date and To date along with any one of the following statuses:

• Succeeded
• Running
• Failed
• Cancelled
• Waiting
• Skipped
• Suspended
• Paused
• Timed Out
• Aborted

Search by Identifier

Search by Identifier allows users to retrieve the run details for the identifier they input.

Get Retry Chain by identifier

Users can get the Retry chain by entering the run Identifier.

Apart from this optional setting, users can also get the retry chain by clicking on the tag next to the run identifier.

Resubmit failed Logic App runs

A Logic App run would fail due to failure in one of its actions and it occurs quite often in a business orchestration. Turbo360 already facilitates viewing the run history and accessing the details of the failed runs.

As a value add to enhance Logic Apps management, Turbo360 now brings in the capability to resubmit the runs from the Run History.

Though run resubmission is possible in the Azure portal, the challenge is a lack of clarity in identifying the resubmitted runs.

Turbo360 overcomes this challenge by adding a tag that brings in the details of the original parent run to those runs which are resubmitted either from Turbo360 or from Azure Portal. An additional tag gets added to the parent run that retrieves the list of all child runs.

Ignore runs

It is possible to ignore logic app runs in bulk and a tag will be associated with the specific runs along with a description. This ignore tag is visible only in Turbo360. It will not have any impact on the actual runs.

Trigger history

Users can view all the triggers to the Logic App along with details about the inputs and outputs of each trigger. If there are multiple triggers, the trigger history can be filtered by the trigger, as in Azure Portal.

The triggers can also be filtered based on the following statuses:

• Succeeded
• Running
• Failed
• Cancelled
• Waiting
• Skipped
• Suspended
• Paused
• Timed out
• Aborted

Action required

Action required helps users to focus on the failed Logic App runs.

It also enables them to resubmit as well as ignore the failed runs.

Action required runs widget

Turbo360 now includes Count Chart widget support for the Action required runs metric, allowing users to identify the number of failed runs that require any action to be performed within a specified time interval.

Resubmission should be done only from Turbo360 in order to get more accurate results for this Dashboard widget. Resubmitting from the Azure portal will have no effect on the Action required runs Count Chart widget.

Favorite runs

Any of the Logic App runs used frequently can be marked as a favorite along with an optional description from both Run history as well as Action required tabs.

Multiple runs can be marked as favorite at once. Users can also remove a particular run from favorites in the Favorite runs tab.

Inline task

In the Logic App section, users can create a really quick task to resubmit failed runs from the source logic app that is being explored.

The configuration created to run immediately can also be saved for future use in the Automated tasks section.

Inline task to resubmit failed runs

This feature allows users to quickly resubmit the runs that failed within the specified hours (Minimum 1 hour).

The following illustration resubmits the failed Logic App runs in last 10 hours:

Task status can be viewed by navigating to Automated Tasks section and switching to Task history tab.

Automated task

Consider an employee management scenario, where the employee joining process in an organization is defined in a Logic App. When an employee joins an organization, a message with required employee details will be pushed into a Service Bus Queue by the HR application.

A Logic App will be listening to the Service Bus Queue for messages.

Whenever a message arrives in the Service Bus Queue, the Logic App will extract the message body of the Service Bus Message and post it to an Azure Function and store it in a Storage Table for future references.

The Azure Function will process the Employee details and assign them to the required departments in the organization.

In the example above, what if the Logic App encounters an error and needs to be resubmitted to fix it?

Turbo360's Automated tasks allow users to configure resubmitting of failed runs for a specified time.

The following illustration resubmits the failed logic app runs using Automated task:

Resource Dashboard

A default resource dashboard is available for Logic App resources in the Overview section, allowing for enhanced data visualization and tracking of real-time data.

Users are provided with the following pre-defined Dashboard widgets, which can be customised to meet their specific needs.

1. Total Billable Executions
2. Runs started
3. Runs Failed
4.Run Failure Percentage
5. Action Summary
6. Trigger Summary
7. Run Summary
8. Action Success Vs Failure
9. Trigger Success Vs Failure
10. Run Success Vs Failure
11. Consumption By Type
12. Failure Summary
13. Performance By Latency
14. Success Latency

Monitoring

Logic App metrics and failure count can be monitored using Turbo360.

Metric Monitoring

1. Navigate to Logic App -> Monitoring to configure the monitoring rules for Logic Apps
2. Select the necessary monitoring metrics and configure the threshold values
3. Click Save

The threshold values can also be provided with any metric name, defining the monitoring rule to be violated when the metric value configured at threshold field is met.

Failure Monitoring

1. Navigate to Logic App -> Monitoring to configure the monitoring rules for Logic Apps
2. Select Failed runs under Failures and configure the threshold values
3. Click Save

Monitoring Recommendations

This section contains the common settings for monitoring Logic App consumption.

State

The below picture shows how to configure the monitoring for the state of your Logic App to be in the enabled state. Note you can also configure an auto-correct state to make Turbo360 change it back to enabled if it is disabled.

Failures

Failure monitoring will check the run history API for your Logic App. In this case you can configure the number of errors since the monitoring last checked the API which would trigger the alerts that your Logic App is unhealthy. The threshold will vary based on the requirements for your scenario.

Metrics

Because Turbo360 can check the API for run history you do not need to use the metric counter for this monitoring. There are however still some metrics you may choose to monitor such as the ones shown below.

• Run Latency is the average duration of your Logic App runs. If you want to get alerts if this metric is changing from the normal value then you may want an alert
• Triggers Failed is a common metric is you are doing something like polling service bus and you have a connectivity error you would see this counter increase