Today, as more customers are adopting Azure workloads, and extending the reach of their on-premises integration solutions and existing assets to cloud services, it becomes inevitable to have all these disparate resources monitored in one place through a hybrid solution.
Logic Apps is Microsoft’s cloud-based integration framework that allows developers to easily design workflows and leverage a wide range of connectors. As with other Azure resources, Logic Apps are equipped with built-in diagnostic logs and metrics that are meant for developers and power users to diagnose issues for a specific resource in Azure portal at a given time.
It is also worth mentioning that there are also centralized monitoring services provided by Azure that targets different levels of resources’ monitoring, such as Operations Management Suite (OMS), Application Insights, and Azure Monitor.
Monitoring across on-premise and cloud solutions
AIMS monitoring platform has the capability to monitor Logic Apps in addition to Windows Server, BizTalk Server, and SQL server agents. Using AIMS, you also get anomaly detection capabilities into your arsenal that could span across your on-premises and cloud solutions, in addition to the traditional monitoring. Check my previous post for more details about AIMS monitoring platform and AIMS Anomaly detection post.
In this post, I will focus on the monitoring aspect for Logic Apps, I have yet to test the anomaly detection for Logic Apps, as AIMS initially needs 2 weeks of ingesting metrics, before detecting anomalies.
Getting up and running with Logic Apps monitoring
You can easily create and configure a Logic App SaaS agent in your AIMS platform, and integrate it with your Logic App using a newly registered Azure AD application.
Once configured it will start collecting the main metrics for the run statuses, and latency for the Logic Apps Actions, Triggers, and the overall workflow, which could be very useful.
For instance, an increasing rate of Action failures might indicate that there might be an issue with an underlying managed API, while a higher latency might indicate a downstream system bottleneck, or may be, a non-optimized custom code in your Azure function that needs a fix.
As you can see, because Logic Apps is a serverless PaaS, the underlying infrastructure is invisible to us, and in turn, this makes the monitored metrics at a higher level, focused on the workflow actual runs without any underlying infrastructure metrics.
One final note, to get the most out of AIMS platform for your hybrid solution, you can add the Logic App agent to your existing topology in AIMS platform, this will allow you to monitor and detect errors that coincides and spans across your different hybrid solution components.
In the above picture, AIMS Topology in my platform had already defined BizTalk Server, SQL Server, and Windows Server agents, and I added the newly created Logic App agent to it.
This blog post was originally published on Ahmed Taha's technical blog, To Integration and Beyond on 15 July 2018.
Topics from this blog: Blog