Configuring the Azure Logic Apps Logging and Monitoring Agent

Info

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

• Subscription Configuration - Learn how to configure a Subscription with Logic App Workflows, Event Hub connectivity, and Resource Groups to include in Monitoring and Logging.
  • Event Hubs - Connect to the diagnostics Event Hub that Logging and failed-run monitoring both read; it can live in a different subscription than the workflows.
  • Logging - Choose which triggers, Actions, and payloads become Log Events.
  • Workflow Monitoring - Set Non-Events thresholds and exclude workflows from Monitoring.

Note

Monitoring and Remote Configuration become available after you install the agent and create its initial Monitoring Agent Configuration. First-time users start at Add Azure Logic Apps Configuration.

The agent needs an App Registration to connect to the Azure REST APIs. During subscription setup, you can also configure some features with SAS/connection-string options, depending on version and scenario; see Azure access in the Prerequisites and review Azure Application Access - Least Privileges before you configure authentication.

Understanding the configuration

You configure the agent remotely from the Web Client. The Monitoring Service passes your changes to the agent, which then reads Azure and feeds Nodinite with state and Log Events:

Diagram: You open the Remote Configuration in the Web Client (blue). The agent (orange) keeps global settings on the Settings tab and one entry per Azure Subscription (teal), each with its own Event Hubs, Logging, and Workflow Monitoring settings.

Remote Configuration

As a Nodinite Administrator, click the 'Configuration' button to open a modal for Remote Configuration and configure the Monitoring Agent:

Click the 'Configuration' button to open a dialog for configuring the agent.

You can perform specific configurations directly on Resources using the Action button, given that the Role of the Monitor View has the Remote Actions feature enabled; see Managing Logic Apps.

Info

You must be a Nodinite Administrator to manage Azure Subscriptions with Azure Logic Apps.

Settings tab

From within the Settings tab, you provide some details that determine the operation behaviour of the Azure Logic Apps Logging and Monitoring Agent.

• Environment
• Debug
• Culture Information
• Agent database connection string
• Days to keep successful workflow runs
• Days to keep running and failed workflow runs

The Settings tab, here with the Swedish (sv-SE) culture and the default retention days for workflow runs.

Environment

As part of the common features shared with all Monitoring Agents is an option to set the name of the target Environment, for example, TEST, QA, PROD.

Debug

Part of the common features shared with all Monitoring Agents, is an option to set the Debug flag for additional file logging that you can enable or disable as needed. Default is unchecked.

Culture Information

The Culture Information setting determines how the Web Client and Web API present time-based data from this Agent.

Note

This setting applies to the date and time values this agent formats. Apart from those, the Web Client shows dates and times in your browser's local format, and the Web API returns them in UTC.

Agent database connection string

The Nodinite Azure Logic Apps Logging and Monitoring Agent uses a SQL Server Agent Database to store data, including retry counts for resubmitting failed runs—a unique Nodinite feature. The service identity needs the SQL Server rights listed in the Prerequisites.

Server=localhost;Database=Nodinite_Agent_AzureLogicApps;Integrated Security=true;Connection Timeout=60;TrustServerCertificate=True

The connection string uses Microsoft.Data.SqlClient with modern TLS defaults.

Tip

Need help with connection strings? See the comprehensive SQL Server Connection Strings guide for certificate validation, AOAG configuration, troubleshooting, and security best practices.

Days to keep running and failed workflow runs

• Days to keep running and failed workflow runs - Specify the number of days to keep the running and failed runs until marked for deletion in the Agent database (Default = 180 days)

Days to keep successful workflow runs

• Days to keep successful workflow runs - Specify the number of days to keep the successful runs until marked for deletion in the Agent database (Default = 7 days)

To keep the long-term history in Nodinite and a short retention in Azure, see Reduce Azure Logic Apps Run History Retention to Lower TCO.

Save

You must click 'Save' or 'Save and close' for changes to persist. The agent evaluates the new settings and thresholds on the next synchronization.

Here's an example of the Save options.

Note

The delay in presenting the new evaluated state depends on the synchronization interval set for the Monitoring Agent. Click the Sync Now button to force an immediate synchronization.

• Save and close, save, and close the dialogue.
• Cancel, closes the dialogue without saving any changes.

Add Azure Logic Apps Logging and Monitoring Agent Configuration

After successfully installing the Nodinite Azure Logic Apps Logging and Monitoring Agent, you must provide connection details so the Monitoring Service knows there's a new guy in town.

There is no Monitoring or Logging in the Azure Logic Apps Logging and Monitoring Agent until you perform the steps below.

Configuration Steps

1. Add and configure a new Monitoring Agent Configuration. Connection information is available in the README.txt file in the installation folder.

2. Use the Remote Configuration feature to configure the Agent. Detailed at the beginning of this user guide.

3. Create one or more self-service enabled Monitor Views that include the selected Resources provided by the Azure Logic Apps Logging and Monitoring Agent according to business needs, and add Alarm Plugins to get notified on state changes.

   • Add or manage Monitor View

4. Fine-tune specific settings directly on Resources using Remote Actions

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

This is detailed in the User access to Logic Apps Monitoring guide, using Monitor Views, Roles, and Users.

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

This is detailed in the User access to Logic Apps Logging guide, using Log Views and Roles. See Logging Logic Apps for what the agent logs.

Frequently asked questions

Find solutions to common problems in the Troubleshooting guide.

Next Steps

• Subscription Configuration
• Add or manage a Monitoring Agent Configuration
• Add or manage Monitor View
• User access to Logic Apps Monitoring

Related Topics

• Azure Application Access
• Prerequisites
• Install Azure Logic Apps Agent
• Update
• Logic Apps Log Agent
• Monitoring Logic Apps
• Logging Service
• Roles