Monitoring Logic Apps

Catch failed runs, disabled Logic Apps, and configuration or deployment mistakes before your business notices them. The Nodinite Azure Logic Apps Logging and Monitoring agent discovers your Logic Apps across every Azure Subscription, evaluates their state against your thresholds, and lets the right people act on problems from a Monitor View, without access to the Azure Portal.

• ✅ Auto-Discovery of Consumption and Standard Logic Apps in all configured Subscriptions
• ✅ State Evaluation with user-defined Warning and Error thresholds
• ✅ Failed runs and failed triggers alerts, with resubmit from Nodinite
• ✅ Configuration watchdog for Subscriptions, Resource Groups, and Log Configuration
• ✅ Remote Actions to enable, disable, and edit thresholds (Managing Logic Apps)
• ✅ Alerts on state changes, pushed outside Nodinite through Alarm Plugins

Tip

Use the Non-Events Monitoring feature on business-critical solutions!

This page describes what Nodinite monitors and the rules for how Nodinite translates this into meaningful monitoring states. Some remote commands are also available as Actions to help you swiftly manage problems; the Managing Logic Apps page details them. To log the business data of your runs, see Logging Logic Apps.

How Monitoring Works

The agent evaluates each discovered Resource, and the Monitoring Service collects the result. Users with access to a Monitor View see the state, act on it with Remote Actions, and receive alerts through Alarm Plugins.

Diagram: The agent evaluates each Logic App into OK (green), Warning (yellow), or Error and Unavailable (red); state changes to Warning or Error raise alerts, and you resolve problems with Remote Actions.

Monitoring Features

• Auto-Discovery

  • Nodinite Azure agents use the Azure REST API and automatically discover your Logic App resources. Sharing access to any individual Logic App resource is easy from within Nodinite using Monitor Views.

• State Evaluation - Make sure the Logic App resources have the intended run-time state!

  • State evaluation for Logic Apps
    • Enabled/Disabled - Get alerted if anyone disables your Logic App
  • Failed run evaluation - When Monitoring is enabled, get alerted when runs fail (Configuration - Workflow Monitoring)

    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 types of Logic Apps artifacts, Nodinite groups the monitored Resources by Categories
  List of categories being monitored.

• Logic App Workflows

• ❌ Failed Runs

• Failed Triggers

• Log Configuration

• Subscription

• Resource Group

Logic App Workflows

Each Logic App Workflow discovered in the Logic App Category appears within Nodinite as one Resource. If you have 42 deployed Workflows, then you have 42 Resources in Nodinite.

List of Logic App Workflows in a Monitor View.

• The name of the Resources comes from the name of the deployed Logic App
• All Logic Apps belong 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

Here's an example of the Nodinite Application naming pattern.

Note

Logic Apps Standard have the Web Site name as suffix in the naming scheme.

Each presented Logic App Workflow has one of the following evaluated monitoring states at any given moment:

Logic app example when too few executions exist within the current lookback timespan.

From within Nodinite, you can reconfigure the state evaluation on the Resource level using the Expected State feature. Set the default thresholds for all workflows in Configuration - Workflow Monitoring.

Failed runs

The Nodinite Azure Logic Apps Logging and Monitoring agent evaluates the outcome of runs. One virtual resource is available within the Monitor Views that include it.

Here's an example of an Error when there are one or more failed runs.

Whenever a run fails, Nodinite evaluates the Resource as being in state Error. It remains in this state until you clear the error.

• Manage failed runs
  • Resubmit failed runs
• Clear failed runs

Note

The Monitoring feature requires operational Azure diagnostics for the failed runs evaluation to work; see Prerequisites - Logic Apps and Configuration - Event Hubs.

To search and archive the failed runs themselves, use Logging Logic Apps with the Log Status Code Search Field.

Failed Triggers

Similar to Failed Runs, the Nodinite Azure Logic Apps Logging and Monitoring agent evaluates the outcome of trigger executions. One resource is available within the Monitor Views that include it.

Whenever a trigger fails, Nodinite evaluates the Resource as being in state Error. It remains in this state until you clear the error.

The following Remote Actions are available:

• Manage failed triggers
  • Resubmit failed triggers
• Clear failed triggers

Note

The Monitoring feature requires operational Azure diagnostics for the failed triggers evaluation to work.

Resource Group

For each configured Azure Subscription, you manage the set of named Resource groups to include in the Monitoring (Resource groups tab). The Resource Group Category presents each of these. Each such monitored configuration appears as a Resource in Nodinite to help you make sure the Monitoring is operational.

Here's an example of monitoring the 'Resource Group' Category as seen in a Nodinite Monitor View.

Example with a missing 'Resource Group'.

This feature exists because customers had business-impacting incidents when people (usually developers) or automated deployments accidentally renamed or even deleted the Azure Resource Group.

List of Remote Actions available for the Resource Group Category:

Remote Actions available for a Resource Group Resource.

• Details
  • Inactivate - This Action is available only when the Resource Group is missing
• Statistics

Subscription

Tip

Use the Details Action to manage the set of Resource Groups to include in the Monitoring and Logging.

Each configured Azure Subscription (Configuration - Subscription) manifests as one Resource of the Subscription Category.

Here's an example of monitoring the 'Subscription' Category as seen in a Nodinite Monitor View.

Example with a Subscription in the OK state.

List of Remote Actions available for the Subscription Category:

Remote Actions available for a Subscription Resource.

• Details
• Statistics

Log Configuration

The Log Configuration category helps you monitor both the agent Configuration and the Azure configuration. You must match the configuration in Azure with the agent Configuration (Configuration - Logging).

Here's an example of the Log Configuration Category.

List of Remote Actions available for the Log Configuration Category:

Remote Actions available for a Log Configuration Resource.

• Details

Alert history for Logic Apps

During root cause analysis or other purposes, it helps to understand how often your Logic Apps problems happen. 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. The generic instructions on how to Add or manage Monitor View detail this topic.

Search	Resource history
Search for alert history for all resources in the Monitor View	Alert history for the selected logic app

Frequently asked questions

Use the Troubleshooting guide to find the FAQ and answers to known problems.

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

The User access to logic apps monitoring guide details this topic.

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

The 'User access to logic apps logging' guide details this topic.

How do I enable monitoring of Logic Apps

To monitor Logic Apps, configure the agent for each Subscription with the Enable monitoring checkbox checked for each Resource Group to monitor (default is checked). The Configuration - Subscription page and the 'User access to logic apps monitoring' page detail this further.

The image below is from the Remote Configuration form available from the Subscription Details modal.

Example with monitoring for Logic Apps enabled.

Next Steps

• User access to logic apps monitoring
• User access to logic apps logging
• Managing Logic Apps
• Alarm Plugins

Related Topics

• Azure Logic Apps Logging and Monitoring agent
• Prerequisites
• Configuration
• Logging Logic Apps
• Monitor Views
• Resources
• Categories
• Applications
• Non-Events Monitoring
• Troubleshooting