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
The Monitoring Agents Overview page lists all manageable and configured Monitoring Agents.
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.
- As a Nodinite Administrator, click the Monitoring Agent Configuration you want to manage.
- Then, click the Configuration button to open the Remote Configuration Modal.
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.
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
All Nodinite Monitoring Agents converted to .NET 10 include support for AI Diagnostics. 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
Learn more in AI Diagnostics.
Settings tab
All Nodinite Monitoring Agents have a Settings tab for the agent's global settings. On a current agent it has a Basic tab and a Secret Management tab; the Basic tab holds, for example:
- Global polling interval – How often the agent polls, in seconds (default 60)
- 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)
The exact fields differ between agents; each agent's Configuration page (table below) documents its own.
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.
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: