- 7 minutes to read

Add or manage a Nodinite Monitoring Agent Instance

Nodinite Monitoring Agents connect your business-critical systems to a unified monitoring platform. This guide shows you how to add, configure, secure, and manage Monitoring Agents for resilient, self-service monitoring.

✅ Rapidly connect and configure Monitoring Agents for any environment
✅ Secure communication and remote actions with advanced authentication
✅ Restore, backup, and troubleshoot with built-in diagnostics
✅ Empower your team with self-service monitoring and auto healing
✅ Configured or resources from the Monitoring Agent group by Applications and Categories and provides a clear and logical overview of your monitored systems.

There are two primary ways to add a new Nodinite Monitoring Agent:

Quick Add: Paste a JSON string from the README.txt file in the installation folder.
Add Monitoring Agent: Fill in the form with connection details, security settings, and advanced options.

Add Monitoring Agent Instance Options

Each Monitoring Agent has a user-defined configuration entry. The User must be a member of the Nodinite Administrators' Role to manage these entries.

graph RL subgraph "Host with Monitoring Agents" roMonitorAgent(fal:fa-monitor-waveform Monitoring Agent) ro(fal:fa-lightbulb-on Resources to Monitor) roMonitorAgent --> ro end subgraph "Windows Server" roMonitoringService(fal:fa-watch-fitness Monitoring Service) roMonitoringService --> |Monitoring Agent Configuration | roMonitorAgent end

Diagram: Nodinite Monitoring Service connects to Monitoring Agents and their Resources.

Quick Add

Quickly add a new Monitoring Agent by pasting the Quick Add JSON from the README.txt file in the installation folder.

Paste Quick Add JSON to speed up configuration.

JSON Example

{"Name":"SQL on IBSSMIOLSRV01","Uri":"http://IBSSMIOLSRV01:8000/Nodinite/Monitor/Agent/Database/","XApiKey":"71B32996-908E-1337-417E-E5018FD4A3B4","Description":null,"PollingInterval":60}

Example JSON quick add string from the README.txt file

Click Apply to populate all fields from the clipboard JSON. You can now continue to [Manage](#add-and-manage-monitoring-agent the) and configure the Monitoring Agent.

Add and Manage Monitoring Agent

Name (required): User-friendly configuration name
Description (optional): Description of this configuration
Website (optional): External documentation link

Add Monitoring Agent Configuration form

General tab

The General tab provides essential connection details for your Monitoring Agent Configuration.

General tab for Monitoring Agent Configuration

Connection Tab

Configure the Monitoring Service to communicate with the Monitoring Agent.

Connection tab for Monitoring Agent Configuration

Service URL (required): Address for Monitoring Service to communicate with the Monitoring Agent.
Monitoring Agents can use:
- Local LAN (TCP/IP)
- Service Bus Relaying for remote access
  Find the Service URL in the README.txt file in the installation folder.
Polling Interval (required): How often Monitoring Service polls for Resources. Default is 60 seconds.

Tip
Set the polling interval to match your business needs. Short intervals increase system load.

Security Tab

Configure security for communication between Monitoring Service and Monitoring Agent.

Security tab for Monitoring Agent Configuration

Authentication Key (required): API key or Service Bus Relaying info, found in README.txt
Enable authentication to allow Remote Configuration.
For Azure, use a Shared Access Signature (SAS) key. See Microsoft SAS documentation.

Example SAS key:

SharedAccessKeyName=%RootManageSharedAccessKey%;SharedAccessKey=%SharedAccessKey%;AuthenticationKey=%AuthenticationKey%

Advanced Tab

Configure advanced connection settings.

Advanced tab for Monitoring Agent Configuration

Change default Timeout (default: 120 seconds)
Change default Retry handling for unreliable WAN links

If you need to tweak these settings, review diagnostics or contact support.

Common Problems

If the Monitoring Agent Configuration is invalid or the Monitoring Agent is unavailable, it appears offline:

Offline Monitoring Agent in the list

A warning appears during configuration if the agent is unreachable. The message disappears when connectivity is restored.

Warning for unavailable Monitoring Agent

Monitor Views Tab

^{New 6.0}
Manage Monitor Views using the current Monitoring Agent.

Monitor Views tab for Monitoring Agent

Click Edit to manage a specific Monitor View.
Click Add Monitor View to create a new Monitor View with the agent included.

Resources Tab

The Resources tab lists all Resources provided by the Monitoring Agent. Filter, sort, and view details for each resource.

State: Last reported state
Name: Display name
Description: User-friendly description
Application: Application the resource belongs to
Category: Category the resource belongs to
LogText: Output from last sync
Error Code: Error code from last sync
Included in Monitor Views: Number of Monitor Views containing the resource

List of available resources for Monitoring Agent

Configuration Backups tab

Nodinite automatically backs up the configuration file for each Monitoring Agent.

If you lose a server or make a mistake, you can restore previous configurations. Use the Comment feature to document changes.

Info
Configuration backup checks run every 4 hours.

Nodinite Monitoring Service removes old backups automatically. See DaysToKeepMonitorAgentBackups for details.

List of available backups for Monitoring Agent

This feature is fully supported in Nodinite 6. Older versions may not update the 'Config version' column until migration.

Download backup

Download a configuration file by selecting a backup and choosing Download from the Actions menu.

Download backup for Monitoring Agent

Important
Old backups may contain sensitive data. Do not leave copies on the file system.

Restore backup

Restore a configuration with the same version as the current one. Select the backup and choose Restore from the Actions menu.

Restore backup for Monitoring Agent

You will be prompted to confirm the restore:

Confirm restore operation

Click Yes to restore, No to abort.

A success alert appears at the top of the page:

Restore succeeded alert

Important
Restoring an old configuration can drastically change monitoring. Only proceed if you are certain.

To restore an older version, stop the agent, replace the Settings.json file, and restart the Monitoring Agent. Contact support if you need help.

Edit Pin & Comment

Pin or comment on any backup. Select the backup and choose Edit Pin & Comment from the Actions menu.

Pin or comment on backup for Monitoring Agent

Tip
Pinned backups are never removed. Add a comment to explain why you kept it.

Delete backup

Permanently delete any backup. Select the backup and choose Delete from the Actions menu.

Delete backup for Monitoring Agent

Control buttons

The Control panel provides three buttons:

Configuration: Open Remote Configuration.
Sync now: Force Monitoring Service to synchronize immediately.

Successful synchronization example
Diagnostics: Download a ZIP with diagnostic files and info.

Downloaded ZIP with diagnostics

Example ZIP content: Nodinite optimizes disk and network usage

The info.txt file:

Nodinite diagnostics files that could contain vital information that could help us solve problem, attach this file in case you need to contact our support at support@nodinite.com  

Assembly Information  
Name: Nodinite.MonitoringAgent.IBMMQ  
Version: 5.0.0.0  

This file was automatically generated 2019-05-17 13:37:00 +02:00

Example content in the info.txt file part of the ZIP package