- 3 minutes to read

Step 7: Import Monitoring Agents

Import Monitoring Agents configuration into the Portal from the JSON exported in the previous step.

Important

Only agents installed on the local server are supported. The Portal currently supports a single server per environment. If the JSON contains agents from multiple hostnames, you must filter it down to only one server before uploading.

Prerequisites

Steps

  1. In the Portal environment modal, navigate to the Import Monitoring Agents step
  2. Paste the JSON into the text area

Import Monitoring Agents JSON text area in Portal
Example of the Import Monitoring Agents step in the Portal showing the JSON text area with agent entries. Each agent entry includes UniqueId, ServiceURL, Version, AgentType, Name, and ServiceAccount fields.

  1. Click Parse & Filter Agents to validate and parse the JSON

    The Portal analyses the JSON and, if agents from more than one hostname are found, presents the Select Hostnames to Keep screen:

Select Hostnames to Keep – filter to local server
Example of the hostname selection screen shown when the JSON contains agents from multiple servers. Select only the hostname(s) that refer to the local server (localhost or its server name), then click Confirm Selection. All agents not on the selected hostname will be removed.

  1. If the hostname selection screen appears:

    • Select only the hostname(s) that refer to the local Nodinite server (e.g., localhost or the server's machine name)
    • Deselect any hostnames belonging to remote servers
    • Click Confirm Selection to remove remote agents from the list
    • Click Start Over if you need to paste a corrected JSON instead

    Note

    You may see multiple hostnames that refer to the same server (e.g., localhost and the actual machine name). You can keep both — the Portal resolves them to the same machine. Only one agent per agent type is allowed per environment.

  2. Review the filtered agent list and verify:

    • Only agents on the local server remain
    • No duplicate agent types exist (only one agent of each type is permitted)
    • The UniqueId field is populated on each agent entry

  3. Click Upload & Save to save the agent configuration

  4. Click Next to proceed

Completion Checklist

  • JSON pasted into Portal
  • Parse & Filter Agents clicked
  • Only local server hostname(s) selected
  • No duplicate agent types in filtered list
  • UniqueId verified on all entries
  • Upload & Save completed successfully
  • Next button clicked

Next Step

Troubleshooting

"Invalid JSON" Error

Problem: Portal rejects the JSON with a validation error after clicking Parse & Filter Agents.

Solution:

  • Verify JSON syntax is valid (use an online JSON validator)
  • Check for missing commas, brackets, or quotes
  • Ensure the UniqueId field is present on each entry
  • Re-export from the Web Client if the JSON appears corrupted

Upload Fails or Times Out

Problem: Upload & Save button does not respond or the request times out.

Solution:

  • Check the Portal session has not expired (log in again)
  • Ensure only local agents remain — reduce JSON size by removing remote agents
  • Try a different browser

Duplicate Agent Type in List

Problem: The filtered list contains two or more agents of the same type.

Solution:

  • Manually edit the JSON before pasting to keep only one agent entry per agent type
  • Re-paste and re-parse