Configuring the Nodinite Azure Monitoring Agent

Unlock the full power of Nodinite by configuring the Azure Monitoring Agent for your Azure EAI services. This guide walks you through every step, so you can efficiently monitor, manage, and optimize your Azure resources.

• ✅ Configure monitoring for all key Azure resources in one place
• ✅ Empower teams with self-service and remote configuration
• ✅ Fine-tune settings for business and technical needs
• ✅ Ensure secure, role-based access and compliance

Follow these instructions to configure the Nodinite Azure Agent.

Understanding the Remote Configuration

You never edit configuration files on the agent server. A Nodinite Administrator opens the agent's configuration in the Web Client; the Monitoring Service sends the changes to the agent (Remote Configuration). The agent then uses the App Registration of each Subscription to discover and monitor the Azure resources in the selected Resource Groups:

Diagram: The Administrator configures the agent (orange) through the Web Client and the Monitoring Service (blue). The agent reaches each Subscription and its Resource Groups (teal) with the App Registration, and the results appear as Resources in Monitor Views.

Configuration components

Remote Configuration vs Remote Actions

What you can add or manage

• Subscriptions (Monitoring Subscription)
• Resource groups (Monitoring Resource Group)
• API Management Services
• Application Insights
• App Registration
• Certificates
• Container Apps
• Data Factories
• Event Grid Topics
• Event Hub
• Functions
• Key Vault
• Storage accounts
• Web Jobs - Continuous
• Web Jobs - Triggered

Before you begin

Meet the Prerequisites (App Registration, Azure RBAC roles, and firewall ports) and install the agent.

Note

You must first install and create the initial Monitoring Agent Configuration for the Azure Agent. See Add Azure Agent Configuration if you are a first-time user.

Remote Configuration

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

Click the 'Configuration' button to open a modal and configure the agent.

Use the Action button to adjust configurations on the Resource if the Monitor View has the Remote Actions feature enabled.

Add Subscription

Add one or more Subscriptions by clicking the Add button in the Azure Monitoring tab.

Click the Add button to add a Subscription to monitor.

Expand the accordion to view the subscription entry.

Each Subscription appears in the list. Click the accordion to expand the entry.

Assign a unique name to each configuration entry.

Enter a name for the Subscription configuration.

Add Web Jobs

Provide Azure access information. Follow the 'Azure Applications Access' user guide if you have not yet configured and created an Azure AD application and service principal that can access resources.

For role assignment and scope recommendations, review AzureApplicationsAccess - Least Privileges.

You don't need to change existing solutions!

The Web Jobs tab displays an array with zero or more subscription/resource group entries.

Add your Resource groups for Azure Subscriptions to log and monitor.

• Press the Add button to add one or more Azure subscriptions.
  
  This example shows a subscription configuration with one accordion per configuration.
• Repeat this step for each Azure subscription you want to log and/or monitor with Nodinite.

Configuring the Azure Subscription

Expand the subscription configuration by clicking the Accordion. You can then manage the configuration content.

Add connectivity information. The client secret is masked.

Set the following properties for each subscription:

• Enabled – Check to enable monitoring for this subscription. Unchecked disables all monitoring in this subscription.
• Display Name – Enter a name for this monitoring configuration.

  Info

  This name also serves as the prefix in the application naming scheme.

• Description – Enter a user-friendly description for this configuration.
• Subscription Id – Enter the GUID.
• Tenant Id – Enter the GUID.
• Application ID / Client Id – Enter the GUID.
• ClientSecret – Enter your secret password.

  Important

  If you update a working client secret with a new one, restart the agent to apply the changes. The token is cached for one hour.

Tip

Visit Azure Application Access for more information and to learn how to obtain the required values. Use AzureApplicationsAccess - Least Privileges when assigning roles and scopes for the App Registration.

Configuring Resource Groups

Click the Resource Groups tab to manage resource groups for monitoring.

• Enabled – Check to enable monitoring for this Resource Group.
• Resource Group – Enter the name of the resource group to monitor.

This example shows configuration of named Resource Groups.

Add as many Resource Groups as you need. Users with Remote Actions rights can also change the set of monitored Resource Groups from the Subscription Details action.

Configuring Triggered Web Jobs

Use the Triggered Web Jobs tab to manage the following monitoring properties:

1. Global – Use default values unless you override them with a specific setting.
2. Specific Web Job settings – Override the global configuration for named Web Jobs.

The Triggered Web Jobs tab with the global and specific configuration sections.

Specific Web Jobs

Override general thresholds with specific thresholds for named Web Jobs.

This example shows configuration of user-defined thresholds for a named Web Job.

Triggered Web Jobs Global configuration

• Enable monitoring – Check to enable monitoring for this configuration.
  
  Enabled when checked, or disabled when unchecked.
• Time-based evaluation – The agent always evaluates time-based thresholds. If you don't want time-based evaluation, set long thresholds.

Warning and Error states reach your team through the Alarm Plugins of the Monitor Views that include the Web Job; see Monitoring Web Jobs.

Triggered Web Jobs Specific configuration

Use the Specific configuration section to name a Web Job and configure individual thresholds.

• App Service Name – Enter the name of the App Service where this specific web job runs.
• Web Job Name – Enter the name of the specific web job.

Example of a Specific Web Job configuration.

All other properties match those described in the global configuration.

Tip

You can more easily perform specific configurations using the Edit threshold menu item on the Actions button in the list of Web Jobs (Resources) with Monitor Views and Remote Actions Option enabled; see Managing Web Jobs.

Continuous Web Jobs

Use the Continuous tab to manage monitoring options for continuous Web Jobs.

Example of a Continuous Web Job configuration.

• Enable monitoring – Check to enable monitoring for this configuration.
  
  Enabled when checked, or disabled when unchecked.

Add Azure Storage

See Monitoring Azure Storage for the monitored Storage accounts, blob containers, file shares, and queues, and Managing Azure Storage for the thresholds you can edit.

Add Data Factory

See Monitoring Data Factory for the monitored Data Factories and pipelines, and Managing Data Factory for the available actions.

Settings tab

Use the Settings tab to provide details that determine how the Azure Agent operates.

The Settings tab has a Basic tab and a Secret Management tab. The Basic tab holds these fields:

• Global polling interval
• Environment
• Allowed Hosts
• Log Level

The Settings tab sits between the Monitoring tab and the AI Diagnostics tab; this example polls every 300 seconds and logs errors only.

Global polling interval

Set how often the agent polls, in seconds (for example, 300).

Environment

Set the name of the target Environment (for example, TEST, QA, PROD) as part of the common features shared with all Monitoring Agents.

Allowed Hosts

Specify which host headers the agent accepts. Use * to allow all hosts, or provide a semicolon-separated list of allowed host names (for example, example.com;*.example.com). This security feature prevents host header attacks.

Log Level

Select the level used for the agent's diagnostics logs (for example, Error). Raise the level while troubleshooting, and lower it again afterwards.

Dates and Times

Dates and times from this agent are shown in your local date and time format in the browser. The Web API returns all dates in UTC, including the data sourced from the agent; the Web Client converts them for display.

Save

Click 'Save' or 'Save and close' to persist your changes. The agent evaluates new settings and thresholds on the next synchronization.

This example shows the Save options.

Note

The Monitoring Service updates the evaluated state based on the synchronization interval set for the monitoring agent. Click the Sync Now button to force an immediate synchronization.

Click Save and close to save and close the dialog. Click Cancel to close the dialog without saving changes.

Add Azure Agent Configuration

After you successfully install the Azure Agent, provide Nodinite with connection details so the Monitoring Service recognizes the new agent.

No one can monitor or configure the Azure Agent until you complete the steps below.

Configuration Steps

1. Add and configure a new Monitoring Agent Configuration.

   Find connection information in the README.txt file in the installation folder.

2. Use the Remote Configuration feature to configure the agent. See the beginning of this user guide for details.
3. Create one or more self-service enabled Monitor Views that include the selected Resources provided by the Azure Agent according to business needs, and grant access with Roles.
   • Add or manage Monitor View
4. Fine-tune specific settings directly on Resources using Remote Actions, or override the evaluation with Expected State.

Next Steps

• Azure Monitoring features
• Add or manage Monitor View
• Monitoring Subscription

Related Topics

• Azure Monitoring Agent
• Prerequisites
• Installing the Nodinite Azure Monitoring Agent
• Add or manage a Monitoring Agent Configuration
• Azure Application Access
• Troubleshooting