With the improvements we made in Logic Apps integration with App insight, we streamlined how various types of Logic Apps associated events get emitted and ingested into Application Insights. This change also improved how they get mapped to existing application insight concepts such as requests, dependencies, and exceptions.
Azure workbooks provides a flexible canvas for data analysis and the creation of rich visual reports within azure portal. Azure workbooks also replace Azure monitoring solutions which we had been using with Consumption Logic Apps to build visual dashboards on top of Log Analytics data from consumption Logic Apps.
In this blog post we are going to show how we can use Azure workbooks together with recent improvements to application insight integration to build similar rich and interactive dashboards for standard Logic Apps.
This sample workbook template can be used to create a dashboard that would allow querying and filtering runs based on status and client-request-id. The dashboards can be made interactive where a run can be selected to drill into associated actions and dependencies as well as to bring-up the Logic App monitoring view to show the full details of a run in a familiar view.
Deploying Workbook Template.
The sample template is published here, and we can deploy this workbook template from the azure portal:
Mapping Logic App to Workbook
Once deployed, we can create an instance of the workbook using the template by specifying the subscription, application insight and the logic app resource to be associated with the workbook
using the declared parameters. Please note that you need to have the App-Insight enabled for this logic app and have application insight v2 integration enabled.
Filtering Workflow Runs
Once you have created an instance of the template, the workflow name drop down will be populated with the list workflows that have emitted run start/end traces into the associated Application Insight resource. The status and client-tracking-id parameter fields can be used to filter the runs based on run status or client-tracking-id.
The first table will list all the runs matching the filtering criteria and the result is backed by a query that runs against the app-insight data. This table also leverages the workbook custom-link feature to provide a view link to bring-up the monitoring view and also enable you to resubmit a selected run.
Actions, Dependencies and Exceptions
The second table shows the list of action requests associated with the selected run from the first table and third table will list the associated dependencies if any.
The data listed in this workbook is retrieved using Kusto queries and you can extend and customize this workbook to fit into your needs by editing the underlying queries.