- 4 minutes to read

Monitoring Logic Apps

Learn how to monitor and deal with failed runs and disabled Logic Apps

This section describes what's being monitored and the rules for how Nodinite translates this into meaningful monitoring states. Also, some remote commands are available as Actions to help you swiftly manage problems. Actions are further detailed in the Managing Logic Apps page.

Monitoring Features

  • Automatic Discovery
    • Nodinite Azure agents make use of the Azure Rest API and offer you an automatic discovery of your Logic Apps. Sharing access to any individual Logic App is very easy from within Nodinite using Monitor Views.
  • State Evaluation - Make sure the Logic Apps has the intended run-time state!

    If Nodinite can't check the state of your Logic Apps, chances are no one else can use them either

  • Category based monitoring - To help you sort out the different type of ActiveMQ artifacts the monitored Resources are grouped by Categories
    List of categories being monitored

State evaluation for Logic Apps

LogicAppsAsResources List of Logic Apps in a Monitor View

One Logic App will be displayed within Nodinite as one Resource. If you have 42 deployed Logic Apps, then you will have 42 Resources in Nodinite.

  • The name of the Resources comes from the name of the deployed Logic App
  • All Logic Apps belongs to the 'Logic App' category
  • The Application name is based on physical deployment paths. This pattern guarantees uniqueness:
    • subscription name/resource group name/logic app name

Example of Application naming pattern

Each Logic App (represented in Nodinite as a Resource) has one of the following evaluated states at any given moment:

State Status Description Actions
Unavailable Resource not available If the Logic App can't be evaluated either due to network or security-related problems Review prerequisites
Error Error threshold breached Logic App is disabled and/or there are failed runs [Edit thresholds][AIEditThresholds]
Warning Warning threshold breached More Active Instances exists than is allowed by the Warning thresholds level [Edit thresholds][AIEditThresholds]
OK Within user-defined thresholds Logic app is enabled and/or there are no failed runs [Edit thresholds][AIEditThresholds]

Logic app example when not available

The evaluated state may be reconfigured using Expected State override setting that exists on every Resource within Nodinite.

Last run evaluation

The Nodinite Azure Logic Apps Logging and Monitoring agent evaluates the outcome of runs. There will be one virtual resource available within Monitor Views where this resource is included.

LogicAppsLastRunAsResources List of resources of category 'last runs' for each Logic Apps in a Monitor View

Whenever a run has failed, the Resource is evaluated as being in state Error. It will remain in this state until the error is cleared.

Alert history for Logic Apps

During root cause analysis or for other purposes it might be useful to understand how often problems with your Logic Apps happens. If your Monitor View allows it, you can search for historical state changes for the provided time span either for all your Logic Apps or individually. This topic is further detailed within the generic instructions on how to Add or manage Monitor View page.

Search Result

Search for alert history for all resources in the Monitor View

Alert history for the selected logic app

Frequently asked questions

Other common problems and FAQ for the Logic Apps Logging and Monitoring agent can be found in the troubleshooting guide

How do I grant my users access to logic apps monitoring?

This topic is detailed in the User access to logic apps monitoring guide

How do I grant my users access to logic apps logging?

This topic is detailed in the 'User access to logic apps logging' guide

How do I enable monitoring of Logic Apps

To Monitor Logic Apps, the Agent must be configured with the Enable monitoring checkbox checked (default is checked) further detailed in the 'User access to logic apps monitoring' page.

The image below was taken from the remote configuration form available from the Monitoring Agent Configuration administration page.
Example with monitoring for Logic Apps enabled

Next step