Configuring a Subscription in the Azure Logic Apps Logging and Monitoring Agent

Info

This guide teaches how to configure Subscriptions in the Nodinite Azure Logic Apps Logging and Monitoring Agent to enable Monitoring and Logging of Logic Apps. Please read the 'About Logic Apps Logging options' user guide before you continue.

• The basic configuration is documented in 3. Configuration.

Add Azure Subscription with Logic Apps

Important

Azure access information is required; follow Prerequisites - Azure access and the 'Azure Applications Access' user guide first if you have not yet created an App Registration in Microsoft Entra ID with the required roles.

When assigning access, follow AzureApplicationsAccess - Least Privileges.

The Logic Apps tab has an array with one or more Subscription configurations for Resource Groups, Workflows, Event Hubs, Authentication, and payload Filter Configurations. Add your Azure Subscriptions to Log and Monitor

• Press the Add button to add one (or more) Azure subscription(s): Here's an example of a Subscription configuration entry.

• Repeat this step for each of your Azure subscriptions to Log and/or Monitor with Nodinite

Click the Accordion to expand the subscription configuration, and you can then manage the content of the configuration. Example with configuration tabs

Configuration tabs at a glance

Tab	Purpose	Documented on
Basic	Enable the configuration and give it a name	This page
Logging	Choose which triggers, Actions, and payloads become Log Events, for successful and failed runs	Configure Logging
Resource groups	Choose which Resource Groups to monitor and log, and override the Logging filters per Resource Group	This page
Workflows	Enable workflow monitoring, exclude workflows, and set Non-Events thresholds	Configure Workflow Monitoring
Event Hubs	Connect to the Event Hub that receives the Logic Apps diagnostics, used by Logging and by failed-run monitoring	Configure Event Hubs
Authentication	The App Registration the agent uses for the Azure REST API	This page

Basic tab

From the Basic tab, you can enter the basic information about the Azure Subscription configuration with Logic Apps to use:

• Enabled - When checked, this Azure Subscription configuration is enabled
• Configuration name - The User-friendly Name of this Azure Subscription configuration

Logging tab

The Logging tab enables Logging and decides which triggers, Actions, and payloads become Nodinite Log Events, with separate settings for successful and failed runs. Its filters are what keep Nodinite storage small compared with the Azure run history. See Configure Logging.

Resource groups tab

From the Resource groups tab, you can enter information about what Resource Groups to include in Monitoring and the Logging options to use:

There are three additional tabs:

1. Basic tab
2. Successful runs
3. Failed runs

Click the Add button to add a Resource Group.

• Repeat this step as necessary. The list is easier to maintain on the Subscription Resource.

Basic Tab (Resource Group)

Tip

You can supersede the global Logging settings for each individual Resource Group.

You must enter the name of at least one existing Azure Resource Group.

The following fields exist:

• Enable Monitoring - When checked, Monitor the state of Logic Apps in this Resource Group and Failed runs.
• Enable Logging - When checked, Log the Logic Apps in this Resource Group when the Global log setting is Enabled
• Override the global filter Logging settings - When checked, Log the Logic Apps according to this specific filter configuration
• Resource Group name - Name of the Resource Group with Logic apps within this Subscription configuration Here is an example of a bad or changed configuration for a Resource Group to monitor. When you remove, or rename a Resource Group in Azure, you must change the configuration accordingly, otherwise, it will appear as Unavailable.
• Description - User-friendly description

Tip

It is much easier to manage the list of Resource groups from a Monitor View with the Subscription Category.

Click the Details action menu item to open a modal to select which Resource groups to include in the Monitoring and Logging.

Successful Runs (Resource Group)

• Trigger
• Actions

Note

The settings for Successful runs on Resource Group level are essentially identical to the global setting for Successful runs, hence, the documentation is not repeated.

Failed Runs (Resource Group)

• Trigger
• Actions

Note

The settings for Failed runs on Resource Group level are essentially identical to the global setting for Failed runs, hence, the documentation is not repeated.

Workflows tab

The Workflows tab enables monitoring of workflows and triggers, excludes workflows by name, and sets global and per-workflow thresholds for execution counts, Action invocations, and duration. See Configure Workflow Monitoring.

Event Hubs tab

The Event Hubs tab connects the agent to the Event Hub that your Logic Apps diagnostic settings send to. It is required for Logging and for monitoring failed runs. The Event Hub can live in a different subscription than the workflows, for example a central platform subscription; then the Event Hubs are configured on that subscription's configuration, and the workload subscriptions have Logging enabled without any Event Hub entries. A configuration can hold many Event Hub entries, and an environment can have several Event Hub subscriptions. See Configure Event Hubs.

Authentication tab

The Nodinite Azure Logic Apps Logging and Monitoring Agent uses an App Registration to connect with the Azure REST API. The Client requires access rights. This requirement applies even when Event Hub entries connect with connection strings (SAS keys) instead of RBAC. The roles it needs are listed in Prerequisites - Azure access.

Tip

You can also review the Azure Application Access page for additional information and learn how to obtain the values for these mandatory fields. Use AzureApplicationsAccess - Least Privileges when assigning roles and scopes.

From within the Authentication tab, you can enter information about how the Agent connects with the configured Azure subscription:

You must set the following properties for each Azure Subscription:

• Subscription ID
• Tenant ID
• Client ID (Application ID)
• Client Secret

Logic Apps

When Monitoring is enabled, the Nodinite Azure Logic Apps Logging and Monitoring Agent evaluate the outcome of runs. If a run fails only once, the Resource for that particular logic with category Logic App - Runs is in the Error state until the error has been cleared, either manually using the Remote Action clear or an Auto Healing operation sets the Clear Date Time property (to the point in time when the action was executed...).

This record creates automatically by the system on the first run failure. If you need to alter the time, this is the place to do so.

---

Next Steps

• Configure Event Hubs
• Configure Logging
• Configure Workflow Monitoring
• Add or manage a Monitoring Agent Configuration
• Add or manage Monitor View
• User access to Logic Apps Monitoring

Related Topics

• Azure Application Access
• Configuration
• Install Azure Logic Apps Agent
• Logic Apps Log Agent
• Logging Service
• Roles
• Reduce Azure Logic Apps Run History Retention to Lower TCO