- 8 minutes to read

What is a Nodinite Monitoring Agent?

Achieve true end-to-end monitoring across your entire integration landscape—from on-premise to cloud—with Nodinite Monitoring Agents. These powerful data collectors enable self-service operations, proactive alerts, and automated problem resolution for business and technical users alike.

Why Nodinite Monitoring Agents stand out:

  • ✅ Universal compatibility - Monitor any technology: BizTalk, Azure, AWS, MuleSoft, Windows Services, databases, APIs, queues, and more
  • ✅ Deploy anywhere - On-premise Windows servers, Azure, Linux, IoT devices—even Apple devices via Node.js
  • ✅ End-to-end visibility - Monitor every link in your integration chain with a unified approach
  • ✅ Self-service empowerment - Business users access real-time status in Monitor Views without IT intervention
  • ✅ Proactive automation - Remote Actions and Auto Healing eliminate manual intervention
  • ✅ Bandwidth optimization - Intelligent caching (etag) minimizes costs and maximizes performance
  • ✅ Flexible connectivity - TCP/IP for local/VPN or Service Bus Relaying for any network
  • ✅ AI-assisted troubleshooting - Agents converted to .NET 10 support AI Diagnostics (set up on the agent's AI Diagnostics tab)

The Monitoring Agent Architecture

graph TD subgraph "Monitored Systems" BT["fa:fa-server BizTalk Server"] AZ["fa:fa-cloud Azure Services"] WIN["fab:fa-windows Windows Services"] DB["fa:fa-database Databases"] API["fa:fa-code APIs"] end subgraph "Monitoring Agents" MA1["fa:fa-monitor-waveform Agent: BizTalk"] MA2["fa:fa-monitor-waveform Agent: Azure"] MA3["fa:fa-monitor-waveform Agent: Windows"] MA4["fa:fa-monitor-waveform Agent: Database"] MA5["fa:fa-monitor-waveform Agent: Custom"] BT -->|"Collects data"| MA1 AZ -->|"Collects data"| MA2 WIN -->|"Collects data"| MA3 DB -->|"Collects data"| MA4 API -->|"Collects data"| MA5 end subgraph "Nodinite Core" MS["fa:fa-watch-fitness Monitoring Service
Orchestrates agents"] MA1 & MA2 & MA3 & MA4 & MA5 -->|"TCP/IP or
Service Bus"| MS end subgraph "Self-Service Access" MV["fa:fa-display Monitor Views
Role-based access"] USER["fa:fa-user Business Users
Monitor and troubleshoot"] MS -->|"Displays via"| MV MV -->|"Empowers"| USER end style MA1 fill:#3F827B,color:#fff style MA2 fill:#3F827B,color:#fff style MA3 fill:#3F827B,color:#fff style MA4 fill:#3F827B,color:#fff style MA5 fill:#3F827B,color:#fff style MS fill:#E47528,color:#fff style MV fill:#2678BD,color:#fff style USER fill:#93d16d,color:#000

Monitoring Agents (teal) collect data from any technology and report to the Monitoring Service (orange), which shows it in role-based Monitor Views (blue) for business users (green).

The Nodinite Monitoring Agents help you monitor your entire systems integration chain, end-to-end.

Nodinite uses the concept of Monitoring Agents to monitor Resources on-premise, hybrid and in the cloud. These Resources can be of any service, endpoint or function in the systems integration chain. The design goal here is to monitor all dependencies, end to end, and optionally to provide metrics, alerts and remote actions with relevant and up-to-date information to stakeholders. In addition, to further help organizations create personal independence, the documentation from the Repository Model, including the use of Articles, is tightly integrated with the Monitoring and is readily available.

You can install any number of Nodinite Monitoring Agents on any number of hosts. To separate these from each other, Nodinite keeps track of them by using a Monitoring Agent Configuration. Each entry points to exactly one installed Monitoring Agent; you manage the entries in Add or manage Monitoring Agent.

The Monitoring Service is responsible for communicating with each Monitoring Agent using the connection details set on its Monitoring Agent Configuration, and it discovers the Resources, Applications, and Categories the agent reports.
Monitoring Agents provide run-time information about Resources. Nodinite keeps track of changes, and you can use this data for further analysis and reporting.

flowchart LR subgraph ONP["fa:fa-building On-premise"] BT["fa:fa-server BizTalk Server"] WIN["fab:fa-windows Windows Server"] DB["fa:fa-database Database / SQL Server"] MQ["fa:fa-bars Message Queueing"] IBM["fa:fa-bars IBM MQ"] FF["fa:fa-folder File Folder"] JMX["fab:fa-java JMX / WSO2"] end MS["fa:fa-watch-fitness Nodinite
Monitoring Service"] subgraph CLD["fa:fa-cloud Cloud"] AZ["fa:fa-cloud Azure"] LA["fa:fa-cloud-sun Azure Logic Apps"] D365["fa:fa-users Dynamics 365"] BOOMI["fa:fa-atom Boomi"] MULE["fa:fa-cloud MuleSoft"] end BT <-->|"TCP/IP"| MS WIN <--> MS DB <--> MS MQ <--> MS IBM <--> MS FF <--> MS JMX <--> MS MS <-->|"TCP/IP or
Service Bus Relay"| AZ MS <--> LA MS <--> D365 MS <--> BOOMI MS <--> MULE style MS fill:#E47528,color:#fff style BT fill:#3F827B,color:#fff style WIN fill:#3F827B,color:#fff style DB fill:#3F827B,color:#fff style MQ fill:#3F827B,color:#fff style IBM fill:#3F827B,color:#fff style FF fill:#3F827B,color:#fff style JMX fill:#3F827B,color:#fff style AZ fill:#2678BD,color:#fff style LA fill:#2678BD,color:#fff style D365 fill:#2678BD,color:#fff style BOOMI fill:#2678BD,color:#fff style MULE fill:#2678BD,color:#fff

Representative Monitoring Agents for on-premise systems (teal) and cloud platforms (blue), all governed by the Nodinite Monitoring Service (orange). The Monitoring Service polls each agent and the agent returns the state of its Resources, over TCP/IP or, for agents in other networks, Service Bus Relaying. The list of agents grows over time, with particular focus on Azure technologies; the full list is under Available Monitoring Agents.

The installed Nodinite Monitoring Agents are governed according to a user-defined configuration by the Nodinite Monitoring Service. A Monitoring Agent configuration holds the connectivity (whereabouts) information for a specific instance of the Monitoring Agent.

You can find information about installed Monitoring Agents using the Monitoring Agents Overview available in the Administration section of the Nodinite Web Client.

Monitoring Agents list with Name, Agent Type, Server, Environment, Version, Description, Log Text, and Polling Interval columns (7.10)
Each row is one Monitoring Agent Configuration; the plug icon shows whether the Monitoring Service can reach the agent.

Any Technology, Any Device

A Monitoring Agent can be installed on-premise or in the cloud. The implemented design pattern is generic and provides a foundation for customers and partners to extend and build their Monitoring Agents. In addition, we provide Templates and SDKs for further custom development. Don't hesitate to contact our support at Support page if you are interested in exploring this topic further.

The Nodinite Monitoring Agents are usually a Windows Service that you install on a Windows Server.

  • .NET Framework 4.8 or later running on-premise or in the cloud (.NET 4.8.1 or later is our recommendation), or .NET 10 for agents that have been converted. Different agents have different prerequisites.
    • Windows Server
  • Node.js based running on just about any device
    • Azure ASE as a Web Application
    • Linux
    • Apple
    • IOT devices

Available Monitoring Agents

Each agent has its own documentation under Logging and Monitoring, with Prerequisites, Install, and Configuration pages:

Agent What it monitors
Azure App Registrations, Functions, Storage, Event Hub, Data Factory, API Management, certificates, and more
Azure Logic Apps Logic Apps
Boomi Integrations Boomi Atoms and processes
Database SQL Server, SSIS, Azure SQL Database, PostgreSQL
File Folder SMB, NFS, SFTP, FTP/FTPS
IBM DataPower Gateway IBM DataPower
IBM MQ Queue Managers, queues, channels, listeners
JMX Java applications (also WSO2, see WSO2 Enterprise Integrator)
Log File Parser Log and text files
Message Queueing MSMQ, ActiveMQ, Azure Service Bus, AnypointMQ
Microsoft BizTalk Server BizTalk artifacts, health check, environment
Microsoft Dynamics 365 Dynamics 365
MuleSoft Anypoint Platform Mule ESB, CloudHub
Non-Events Expected messages that never arrive
RabbitMQ RabbitMQ
Web Services SOAP, REST, certificates
Windows Server Services, disks, CPU, memory, IIS, scheduled tasks, event logs, certificates

The complete table with direct links to every agent's Prerequisites, Install, and Configuration pages is in What Monitoring Agents exist?.

Installing and running

You must install and configure the Nodinite Monitoring Agents. Eventually, these need maintenance. Whenever there's a new version available, a Release note is created and you can get an email alert by logging on to the support page and opt to subscribe. The release note for each Monitoring Agent is available on the Nodinite Portal page.

Documentation-wise, all agents generally share the following structure:

  1. Prerequisites
  2. Install
  3. Configure
  4. Update
  5. Uninstall

You need to be aware of the following topics in order to get operational:

Connectivity

The Monitoring Agents must be able to communicate between the installed agent and the Nodinite Monitoring Service.

The Nodinite Monitoring Agents are designed to conserve bandwidth and use etag caching to achieve excellent performance and less costs (money-wise).

All Windows-based agents support a connection to use either of the following:

  • TCP/IP (default) local or VPN access
  • Service Bus Relaying - use when Agents are installed in other networks where VPN or WAN links are not available.

TCP/IP

For both local and VPN access; It is required to provide an authentication key to enable the Remote Configuration. See documentation for the usage of Port 8000. Each agent's Prerequisites page lists the firewall rules it needs.

Service Bus Relaying

Service Bus Relaying - run anywhere. This connectivity type is secure by default.

Service Account Requirements

The account running the Windows Service (Monitoring Agent instance) requires a Windows account and depending on technology additional access rights to cloud- and/or line of business systems (for example SQL, Azure subscriptions, MSMQ, NFS, FTP...).

Logon Rights

On Windows, the account running the Monitoring Agent Service requires special rights, see Logon As A Service for more information.

Access Rights

Depending on the specific agent, see prerequisites within the documentation for each Monitoring Agent.

Diagnostics

If you experience any problems; you can download the diagnostics files as a ZIP package from the Nodinite Monitoring Agents using the Nodinite Web Client. Please attach this ZIP file to our Support page whenever there is a question or an incident. Agents converted to .NET 10 can also analyze their own errors with AI Diagnostics. According to Nodinite policies, these files do not contain any sensitive data like passwords.

Browser download bar with the Nodinite diagnostics ZIP file
Example icon in the browser of downloaded ZIP file with diagnostics information

To increase the verbosity of the agent's logging, set the Log Level on the Settings tab of the Remote Configuration modal (see Remote Configuration). Agents not yet on the Nodinite 7 agent standard (Microsoft BizTalk Server Monitoring, JMX, IBM DataPower Gateway, Microsoft Dynamics 365, and Azure Logic Apps) have a Debug checkbox instead (default unchecked).

Remote Configuration Settings tab with the Log Level drop-down set to Error (7.10)
The Log Level selects how much the agent writes to its diagnostics log; raise it while troubleshooting.

Dates and Times

Agents on the Nodinite 7 agent standard have no date-format setting. The Web Client shows all dates and times in the user's local date and time format in the browser, and the Web API returns all dates in UTC, including data sourced from the 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 Culture Information setting in the Remote Configuration modal, which defines the culturally appropriate format the agent uses for dates and times. See each agent's Configuration page.

Clone

You can host multiple instances of the Nodinite Monitoring Agents either on the same host or on multiple hosts.
This topic is detailed in the Installation of multiple instances on the same server.

Next Steps