- 5 minutes to read

Installing Nodinite Monitoring Agents

Monitor every link in your system integration chain!

With Nodinite, you get end-to-end monitoring of your integration solutions, in the cloud and on-premises, with the ready-to-use Monitoring Agents. Each Monitoring Agent discovers Resources, and the Monitoring Service evaluates their state, raises alerts, and shows them in Monitor Views. This page explains that flow, the installation of Monitoring Agents with Nodinite v7, and what to configure afterwards.

Understanding the Monitoring Flow

graph LR subgraph "Nodinite Core Services Server" roMS["fa:fa-watch-fitness Monitoring Service"] roWC["fa:fa-globe Web Client
Monitor Views"] end subgraph "Nodinite Agent Server" roAgent["fa:fa-monitor-waveform Monitoring Agent"] end subgraph "Target" roRes["fa:fa-lightbulb-on Resources
services, queues, databases, ..."] end roRelay["fa:fa-cloud Azure Service Bus Relay
(optional)"] roPlugin["fa:fa-bell Alarm Plugins
E-mail, Event Log, HTTP Webhook"] roMS -->|"Remote Configuration,
state polling"| roAgent roMS -.->|"across network boundaries"| roRelay roAgent -.->|"outbound"| roRelay roAgent -->|"discover and evaluate"| roRes roMS -->|"state changes"| roPlugin roMS -->|"state"| roWC style roMS fill:#E47528,color:#fff style roAgent fill:#3F827B,color:#fff style roRes fill:#2678BD,color:#fff style roRelay fill:#9E59BB,color:#fff style roPlugin fill:#D5396D,color:#fff

The Monitoring Service (orange) connects to each Monitoring Agent (teal), directly or through an optional Azure Service Bus Relay (purple). The agent discovers and evaluates the Resources (blue) on its target. State changes go to the Alarm Plugins (pink) and to the Monitor Views in the Web Client.

Key Components

Component Role in monitoring Where you manage it
Monitoring Agent Discovers Resources on one technology and reports their state Installed from the Portal package or an MSI
Monitoring Service Synchronizes agents, evaluates state, and sends alerts Core Services
Monitoring Agent configuration Tells the Monitoring Service how to reach the agent Add or manage Monitor Agent in the Web Client
Resources Discovered by the agent; you never create them by hand Monitor Views, Expected State
Alarm Plugins E-mail, E-mail with options, Event Log, and HTTP Webhook Administration → Settings

Choose How Each Agent Is Installed and Reached

Option When to use it What follows
Portal package with the CLI The agent runs on a server in your Portal Environment Register each agent in the Web Client with Quick Add, using the JSON from the generated README.txt
MSI from Download and Update Agents The agent runs on a server that doesn't host the Core Services and is outside the package, for example a BizTalk Server node. The MSI defaults to port 8000 Register the agent with Quick Add
Direct TCP/IP connection The Monitoring Service can reach the agent's port Open the port listed in the Network and Firewall Overview
Service Bus Relay A firewall or network boundary blocks direct connections Use the Nodinite v7 Hybrid Connection string format; the v6 format is obsolete

The full list of Monitoring Agents is on the Monitoring page.

Before You Install Monitoring Agents

Install Monitoring Agents with Nodinite v7

Nodinite v7 installs Monitoring Agents from the same generated package as the Core Services. The Install Nodinite v7 Steps are the master for every field; the steps below show where Monitoring Agents fit in.

Step 1: Add and Configure the Agents in the Portal

  1. In Step 4: Servers, add each agent under Agents on this server for the server that should run it.
  2. In Step 5: Agents, expand each agent card and enter the Server, Port, Service domain, and Service account, plus the sections that agent shows. Give every agent a unique port.

Step 2: Download and Run the Package

Download the package in Step 6: Review and Download, and run it from an elevated PowerShell 7 prompt as described in Step 7: Run the CLI Workflow. To add one agent later, use install-agent.

Step 3: Register Every Agent in the Web Client

On Windows Server, Nodinite doesn't register Monitoring Agents by itself, whether the package installed them with the CLI or you installed an MSI. In the Web Client, open Administration → Monitoring Agents → Add Monitoring Agent, and paste the Quick Add JSON from the generated README.txt (or, for an MSI, the README.txt in the agent's installation folder) into Quick Add.

Step 4: Configure What to Monitor

  1. Open the agent's Remote Configuration in the Web Client and set what the agent monitors, for example which Windows services or queues.
  2. Add the discovered Resources to a Monitor View, and set Expected State where a stopped or empty state is normal.
  3. Select an Alarm Plugin entry on the Monitor View, and grant your users access through a Role.

Important

The v6 Install and Update Tool is deprecated, and Nodinite v6 is no longer supported. If you still run v6, follow Updating from v6 to v7, which also exports and imports your Monitoring Agent configurations.

Previous Step

Next Steps