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.

Understanding the Subscription configuration

The agent doesn't discover your Azure estate on its own. Each Subscription configuration tells it which Azure subscription to read, which credentials to use, and what to do with the Logic Apps it finds there: which Resource Groups become monitored Resources in your Monitor Views, which workflow runs become Log Events in your Log Views, and which Event Hub carries the diagnostics. The Subscription configurations live in the agent's Remote Configuration, so you manage them from the Nodinite Web Client instead of editing files on the agent server.

Diagram: The Remote Configuration (blue) holds one Subscription configuration (orange) per Azure subscription. Its tabs (teal) connect to Azure (purple) and produce the Resources and Log Events (green) that users see in Nodinite.

Configuration tabs at a glance

Global settings vs Resource Group overrides

The Logging filters exist on two levels. Start with the global level, and override it only for the Resource Groups that need something different.

Before you start

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 agent is installed; see Install Azure Logic Apps Agent.
• Your Logic Apps have a Diagnostic setting that sends to an Event Hub; see Prerequisites - Enable Logic Apps Logging in Azure and the ARM Template example.
• The agent can reach Azure, the Log API, and SQL Server; see Prerequisites - Firewall settings.

Add Azure Subscription with Logic Apps

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 new, empty Subscription configuration entry.

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

Expand the accordion to manage the content of the subscription configuration.
Example of a Subscription configuration with its configuration tabs.

Basic tab

From the Basic tab, you can enter the basic information about the Azure Subscription configuration with Logic Apps to use:
The Basic tab holds the on/off switch and the name of the Subscription configuration.

• 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. It also holds the Log API address and the Log Agent Id that stamps the Log Events; the address comes from your environment's settings (Servers step). Its filters are what keep Nodinite storage small compared with the Azure run history; see Reduce Azure Logic Apps Run History Retention to Lower TCO. For every setting, see Configure Logging.

The Basic tab of the Logging settings; the other Logging tabs are on the Configure Logging page.

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:
The Resource groups tab lists the Resource Groups to monitor and log in this subscription.

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.
Example of a Resource Group entry with Monitoring and Logging enabled.

The following fields exist:

• Enable Monitoring - When checked, the agent monitors the state of the Logic Apps in this Resource Group and their Failed runs; see Monitoring Logic Apps.
• Enable Logging - When checked, the agent logs the Logic Apps in this Resource Group when the Global log setting is Enabled; see Logging Logic Apps.
• Override the global filter Logging settings - When checked, the agent logs 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.

The Details action on the Subscription Resource in a Monitor View.

Click the Details action menu item to open a modal to select which Resource groups to include in the Monitoring and Logging; see Subscription Details.
Select the Resource groups to monitor and log without opening the Remote Configuration.

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. These thresholds are Non-Events checks, similar in idea to Non-Events Monitoring; the agent evaluates them and reports the state to the Monitoring Service. See Configure Workflow Monitoring.

The Workflows tab with its General, Global thresholds, and Specific thresholds tabs.

Event Hubs tab

The Event Hubs tab connects the agent to the Event Hub that your Logic Apps diagnostic settings send to. Logging and the monitoring of failed runs both require it. The Event Hub can live in a different subscription than the workflows, for example a central platform subscription; then you configure the Event Hubs 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, and for the Event Hub and checkpoint storage cost, Azure Costs for Blob Storage and Event Hub.

The Event Hubs tab lists one entry per Event Hub in this subscription.

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. Prerequisites - Azure access lists the roles it needs.

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:
The Authentication tab holds the App Registration credentials for one 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 evaluates the outcome of runs. If a run fails only once, the Resource for that Logic App, in the Logic App - Runs Category, stays in the Error state until someone clears the error. Either a user clears it manually with the clear Remote Action (see Clear), or an Auto Healing operation sets the Clear Date Time property to the point in time when the action ran.

The system creates this record automatically on the first run failure. If you need to alter the time, this is the place to do so.
Example of the per-Logic App record with its Clear Date Time.

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
• User access to Logic Apps Logging

Related Topics

• Logic Apps Log Agent
• Prerequisites
• Install Azure Logic Apps Agent
• Configuration
• Monitoring Logic Apps
• Logging Logic Apps
• Managing Logic Apps
• Azure Application Access
• About Logic Apps Logging options
• Reduce Azure Logic Apps Run History Retention to Lower TCO
• Updating the agent
• Troubleshooting
• Logging Service
• Roles
• Users