- 5 minutes to read

Manage the Remote Configuration for Nodinite Monitoring Agents

Nodinite Remote Configuration empowers you to manage, secure, and optimize Monitoring Agents from anywhere—on-premises, off-site, or in the cloud. This guide shows you how to access and use the configuration modal for seamless, centralized control.

  • ✅ Centrally manage all Monitoring Agents from the Web Client
  • ✅ Secure configuration with role-based access and encrypted connections
  • ✅ Instantly update settings for any environment—test, production, or cloud
  • ✅ Save time with direct access to agent-specific configuration modals

Animation: the Windows Server agent's Remote Configuration, Settings tab, Environment changed from DEMO to Test, Save, a new row on Configuration Backups, and the Configuration reopened showing Test (7.12)
Change a setting, save, and reopen the Configuration to see the value the agent now runs with: the modal is read from the agent each time it opens. Every save also adds a configuration backup.


The Monitoring Agents Overview page lists all manageable and configured Monitoring Agents.

Monitoring Agents list with the Add Monitoring Agent button, Filter the result, Filter on Tag, Include deleted, and the Name, Tags, Agent Type, Server, Environment, Version, Description, Log Text, and Polling Interval columns (7.12)
The plug icon in front of each agent shows whether the Monitoring Service can reach it.

To use Remote Configuration, you must first set up a Secure Connection in the Security Tab. See the Add or manage a Monitoring Agent Configuration guide for details.

  1. As a Nodinite Administrator, click the Monitoring Agent Configuration you want to manage.
  2. Then, click the Configuration button to open the Remote Configuration Modal. The button stays disabled until Authenticate Connection is checked on the Security tab and the page is saved. In the list, the row's Action menu has the same Configuration item.

Control panel with the Configuration, Sync Now, and Diagnostics buttons, Configuration highlighted
Click the 'Configuration' button to open a modal to configure the agent.

The Remote Configuration feature works for Monitoring Agents installed anywhere—even off-site or in the cloud.

Remote Configuration modal for a Windows Server agent with Reload, Sync Now, and an agent tab plus a Settings tab
Generic example of the remote configuration modal.

You can also perform many specific configurations from the Resource view, using the Action button from Monitor Views where Remote Actions are allowed (the Execute Action permission in the Permission Set for Monitor Views).


AI Diagnostics

AI Diagnostics is a tab that the agent itself provides in its Remote Configuration, so only Monitoring Agents converted to .NET 10 have it (for example Azure 7.11.3 and Message Queue 7.11.3; not Windows Server 6.5 or BizTalk 1.0). This feature automatically analyzes errors and warnings from monitored resources, providing intelligent root cause analysis and actionable recommendations to accelerate troubleshooting.

Enable AI Diagnostics on the AI Diagnostics tab of the agent's Remote Configuration (every field is described, with a screenshot, in AI Diagnostics configuration options) to unlock:

  • Autonomous scanning of diagnostics logs
  • Context-aware analysis using local (Ollama) or cloud AI (Azure OpenAI, OpenAI, GitHub Models New 7.x Coming soon)
  • Actionable insights and recommendations to reduce MTTR
  • 100% privacy – logs never leave your infrastructure when using local AI

The analysis runs on the agent's host, against the AI provider set on the tab: AI Provider, Endpoint URL, API Key, Model/Deployment Name, Scan Interval (60 seconds), Max Tokens (1024), Temperature (0.2), and Read All Log Files. It doesn't depend on the AI System Parameter, and it is separate from Nodinite's own AI Assistant.

AI Diagnostics tab of an agent's Remote Configuration with Enable AI Diagnostics checked, AI Provider Azure OpenAI, Endpoint URL (blurred), an empty API Key, Model/Deployment Name, Scan Interval, Max Tokens, Temperature, and Read All Log Files (7.12)
The AI Diagnostics tab of a .NET 10 agent. Without an API Key (or a local Ollama), the agent can't analyze anything.

Learn more in AI Diagnostics.


Settings tab

All Nodinite Monitoring Agents have a Settings tab for the agent's global settings; what it holds depends on the agent. On a current agent (for example Azure or Message Queue 7.11) it has a Basic tab and a Secret Management tab; the Basic tab holds:

  • Global polling interval – How often the agent polls, in seconds (default 60)
  • Outbound proxy – Optional http(s) proxy URL for the agent's outbound calls; empty sends them direct
  • Environment – Name for the environment type (Test/Prod/QA)
  • Allowed Hosts – Which host headers the agent accepts: * for all hosts, or a semicolon-separated list of host names (e.g. example.com;*.example.com); protects against host header attacks
  • Log Level – Level of the agent's diagnostics logs (for example, Error)

Older agents (for example Windows Server 6.5 or BizTalk 1.0) show a flat list instead, with Environment, Debug, and their own settings. Each agent's Configuration page (table below) documents its fields.

Important

Save is refused with Input error(s) while any required field in the agent's configuration is empty, on any tab, so fill in every required field before saving.

Agents on the Nodinite 7 agent standard have no date-format setting: the Web Client shows dates and times in your browser's local date and time format, and the Web API returns all dates in UTC, including data from Monitoring Agents. Agents not yet on that standard (Microsoft BizTalk Server Monitoring, JMX, IBM DataPower Gateway, Microsoft Dynamics 365, and Azure Logic Apps) still have a Debug checkbox and a Culture Information field, which sets the date and time format the agent uses; their Configuration pages document both.

Remote Configuration of the Azure agent: Settings tab with the Basic and Secret Management tabs and the Global polling interval, Outbound proxy, Environment, Allowed Hosts, and Log Level fields (7.12)
The Settings tab of a common agent, next to the agent-specific Monitoring tab and the AI Diagnostics tab.


Monitor Agent configurations

Below are direct links to the configuration modal for each Nodinite Monitoring Agent, together with the agent's own documentation:

Monitoring Agent Documentation Configuration
Azure Azure Monitoring Agent Configuration
Azure Logic Apps Azure Logic Apps Monitoring Agent Configuration
Boomi Boomi Integrations Monitoring Agent Configuration
Database Database Monitoring Agent Configuration
File Folder File Folder Monitoring Agent Configuration
IBM DataPower Gateway IBM DataPower Monitoring Agent Configuration
IBM MQ IBM MQ Monitoring Agent Configuration
JMX JMX Monitoring Agent Configuration
Log File Parser Log File Parser Monitoring Agent Configuration
Message Queueing Message Queueing Monitoring Agent Configuration
Microsoft BizTalk Server BizTalk Monitoring Agent Configuration
Microsoft Dynamics 365 Dynamics 365 Monitoring Agent Configuration
MuleSoft - Anypoint MuleSoft Monitoring Agent Configuration
Non-Events Non-Events Monitoring Agent Configuration
Pickup Log Events Service New 7.0.40 Pickup LogEvents Service Configuration
RabbitMQ RabbitMQ Monitoring Agent Configuration
Web Services Web Services Monitoring Agent Configuration
Windows Server Windows Server Monitoring Agent Configuration
WSO2 Enterprise Integrator (through the JMX Monitoring Agent) WSO2 Enterprise Integrator Monitoring Configuration

Next Steps