- 5 minutes to read

Configuring the Azure Logic Apps Logging and Monitoring Agent

In this section, you will learn how to configure the Nodinite Azure Logic Apps Logging and Monitoring Agent.

Note: Before any monitoring and remote configuration can be performed, you must first install and create a Monitoring Agent Configuration for the Azure Logic Apps Logging and Monitoring Agent. First-time users start here

Remote Configuration

As a Nodinite Administrator, click on the 'Configuration' button to open a modal to configure the agent:

RemoteConfiguration
Click on the 'Configuration' button to open a modal to configure the agent

Many specific configurations can also be made directly on the Resource using the Action button if the Monitor View allows for Actions.

You must be a Nodinite Administrator to Add or Manage the Logic Apps options to monitor

Add Logic Apps

Azure access information is required, follow the 'Azure Applications Access' user guide first if you have not yet configured and created an Azure AD application and service principal that can access resources

No changes to the existing solutions must be made!

The Logic Apps tab holds an array with one or more subscription entries.
RemoteConfigurationSubscriptions
Add your Azure Subscriptions to Log and Monitor

  • Press the Add button to add one (or more) Azure subscription(s):
    EmptyAccordion
    Example subscription configuration, 1 accordion per configuration

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

Configuring the Azure Subscription

Click on the Accordion to expand the subscription configuration and you can then manage the content of the configuration.
RemoteConfigurationSubscription
Add connectivity information, client secret is masked

For each subscription, the following properties can be set:

  • SubscriptionId
  • TenantId
  • ClientId
  • ClientSecret
  • Enable/Disable Monitoring
  • Enable/Disable Logging
    • Log Api URL
    • Log Agent Value Id

TIP: See Azure Application Access page for additional information and learn how to obtain the mandatory values

Enable/Disable Monitoring

  • Enable monitoring, determines if Monitoring of Logic Apps for this configuration is enabled or not
    EnableMonitoring
    Enabled when Checked or Disabled when Unchecked

Enable/Disable Logging

  • When checked logging is enabled. Nodinite needs to know the Log Agent Value Id.
    EnableLogging
    • Enable logging - Enabled when Checked or Disabled when Unchecked
    • LogAPI - The address to the LogApi, for example: http://localhost/Nodinite/Prod/LogApi/
    • Log Agent Value Id - The unique positive integer as Log Agent Value Id in Nodinite so end-users know from which Log Agent data originated. This is further detailed on the Log Agents page

Note: You should not change the LogAgentId once set, since already logged events and messages within Nodinite are already married tp this particular Log Agent Value Id

  • ResourceGroup (collection) - Enter the name of the resource groups to probe for Logic Apps
    ResourceGroups
    Add the names of the Resource Groups to dynamically discover Logic Apps from
    • Repeat this step for each Resource Group*

Logic Apps

When Monitoring is enabled, the Azure Logic Apps Logging and Monitoring Agent evaluates the outcome of runs. If a run fails only once, the Resource for that particular logic with category Logic App - Runs will be in the state Error 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 will automatically be created on the first run failure. If you need to alter the time, then this is the place for such operation.
LogicAppsSetting

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

SettingsTab

Environment

Part of the common features shared with all Monitoring Agents, there 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, there is an option to set the Debug flag for additional file logging that can be enabled/disabled as needed. Default is unchecked.

Culture Information

The Culture Information setting determines how time-based data from this agent is presented in the Web Client/Web API.

Save

You must click Save for changes to be written to the agent and take effect.
png_SaveAndClose

Note: Depending on the synchronization interval set for the agent, there might be a delay before the Web Client reflects upon the change. You can choose to force the agent to synchronize from the configuration of the Monitoring Agent Configuration.

Save and close, saves and closes the dialogue. Cancel Close the dialogue without saving any changes.

Add Azure Logic Apps Logging and Monitoring Agent Configuration

After successful installation of the Azure Logic Apps Logging and Monitoring Agent you must provide Nodinite with connection details so the Monitoring Service knows there's a new guy in town.

No monitoring or other configuration of the Azure Logic Apps Logging and Monitoring Agent is available until the steps below has been followed

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 includes selected Resources provided by the Azure Logic Apps Logging and Monitoring Agent according to business needs.

  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

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

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


Next Step