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 clear instructions to configure the Nodinite Azure Agent.

Add or manage:

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

Note

You must first install and create the initial Monitoring Agent Configuration for the Azure Agent. Start here 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.

You do not 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 for Azure Storage 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.

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.

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 queue settings – Override the global configuration for named Web Jobs.

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 system always evaluates time-based thresholds. If you do not want time-based evaluation, set long thresholds.

State	Name	Data Type	Description
	Warning TimeSpan	Timespan 00:05:00 (5 minutes)	The Web Job must run every configured interval or the system sets a Warning alert.
	Error TimeSpan	Timespan 01:10:00 (1 hour 10 minutes)	The Web Job must run every configured interval or the system sets an Error alert.
	Duration Warning	integer	The system sets a Warning alert if the job runs longer than this value.
	Duration Error	integer	The system sets an Error alert if the job runs longer than this value.

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.

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 queues (Resources) with Monitor Views and Remote Actions Option enabled.

Continuous Web Jobs

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

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

Add Azure Storage

Add Data Factory

Settings tab

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

• Environment
• Debug
• Culture Information

Environment

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

Debug

Enable or disable the Debug flag for additional file logging as needed. The default is unchecked. This is part of the common features shared with all Monitoring Agents.

Culture Information

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

Save

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

This example shows the Save options.

Note

The system 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.
   • Add or manage Monitor View
4. Fine-tune specific settings directly on Resources using Remote Actions.

---

Next Step

• Azure Overview

Related Topics

• Add or manage a Monitoring Agent Configuration
• Add or manage Monitor View
• Azure Application Access
• Installing the Nodinite Azure Monitoring Agent