Logic Apps Monitoring
  • 25 Sep 2020
  • 1 Minute to read
  • Dark
  • PDF

Logic Apps Monitoring

  • Dark
  • PDF

Article Summary

When a Logic App is associated with a Serverless360 Composite Application, it is possible to monitor Logic app in various perspectives using the monitors in Serverless360.

Monitor Logic App State

If the intention is to monitor the state, say the business demands the Logic App, that defines the workflow, to be always enabled, Serverless360 can monitor Logic App state.
By associating a Logic App to Status Monitor or Threshold Monitor, it is possible to monitor the state and alert through configured notification channels by comparing the current state against the expected state. You can read extensive documentation on Status Monitor and Threshold Monitor.

Monitor Logic App based on Metrics

If the intention is to understand the efficiency, reliability or consumption of the Logic App then the choice should be a Serverless360 Data Monitor. Data Monitoring can be configured for a Logic App on an extensive set of metrics. For example to monitor the Logic App run efficiency the Data Monitor can be configured to monitor on a combination metrics like, Run Failure Percentage (%), Runs Started (Count), _Runs Completed _(Count), Runs Succeeded (Count), Runs Failed (Count), Runs Cancelled (Count) with appropriate warning and threshold values set as in figure below
DataMonitor Metrics

If the requirement is to monitor the Logic App consumption then the choice of metrics should be like Billable Action Executions (Count), Billable Trigger Executions (Count), Total Billable Executions (Count)
Data Monitoring documentation can provide more information on this monitor.
Billable Executions

Monitor Logic App for Failure

Serverless360 Watch Monitor can be a solution to get notified on the failure in the trigger or run action of a Logic App. When a Logic App in a Composite Application is associated to a Watch Monitor, can be monitored for failure and the alert will be sent on the configured notification channels within specified duration as low as 5 minutes of the failure occurrence.
Failure detection

We recommend you to read these interesting Use Cases to understand the above mentioned capabilities better

We'd love to hear your thoughts
Please visit our feedback system to suggest new Features or Enhancements. You can also take a look at our Roadmap

Was this article helpful?