- 7 minutes to read

Release Notes

Prerequisites for Mule ESB Monitoring Agent

Unlock the full potential of your Mule ESB and MuleSoft Anypoint Platform with the Nodinite Mule ESB Monitoring Agent. This page outlines everything you need to get started—ensuring a smooth, secure, and efficient monitoring experience for your integration landscape.

graph LR subgraph "Nodinite" roNI(fal:fa-code-commit Mule ESB Monitoring agent) --- roMonitor[fal:fa-monitor-waveform Monitoring] end subgraph "Mule ESB (v3.x)" roMonitor --- |On-Premise|roDB1("fal:fa-random Instances with Nodinite Monitoring Mule Application
(zip)") end subgraph "Cloudhub / Anypoint (v4.x)" roMonitor --- |Hybrid|roCH(fal:fa-cloud Cloudhub Environments) end

Architecture overview: The Nodinite Monitoring Agent supports both on-premise and cloud/hybrid MuleSoft environments for maximum flexibility.

You can deploy the agent on-premise using TCP/IP for local network access, or in the cloud/off-site using Service Bus Relaying ('Azure Relay FAQs').

We recommend installing the agent close to the Nodinite Core Services. This guide focuses on local network setups, typically on the Nodinite application server.

Mule ESB Application (ZIP)

For Mule ESB version 3.x, use this option for on-premise environments. Mule version 4.x leverages public CloudHub APIs.

The Nodinite Mule ESB Monitoring Agent communicates with a Nodinite-specific Mule ESB Application that you install on each Mule Server Instance you wish to monitor. This application provides direct access to the Mule ESB run-time, ensuring comprehensive monitoring and insight.

Verified Topic
Software Requirements
What Windows User Rights does the Nodinite Mule ESB Monitoring agent require?
What Mule ESB User rights does the Nodinite Mule ESB Monitoring agent require?
What Cloudhub user rights does the Nodinite Mule ESB Monitoring agent require?
What Firewall settings does the Nodinite Mule ESB Monitoring agent require?

Software Requirements

This section applies to the Nodinite application server (usually), you will install the Nodinite Mule ESB Monitoring Agent as a Windows Service.

Product Version/Edition
Windows Server Windows 2025
Windows 2022
Windows 2019
Windows 2016
Windows 2012 R2
Windows 2012
.NET Framework .NET Framework 4.8 or later New 6.0
Mule ESB 3.7 and later
MuleSoft ESB Mule runtime engine 4.0 and later
MuleSoft ESB Anypoint platform, on-premise and/or hosted in Cloudhub

Versions 6.0 and later make use of the .NET Framework 4.8 or later.
Version 5.4 make use of the .NET Framework 4.6.2 or later.
Versions before 5.4 make use of the .NET Framework 4.5.2 or later.

What Windows User Rights does the Nodinite Mule ESB Monitoring agent require?

The agent is installed as a Windows Service usually on the Nodinite application server. Virtual machines are supported.

What Cloudhub user rights does the Nodinite Mule ESB Monitoring agent require?

This section is applicable for version 4.x.

The Nodinite Mule ESB Monitoring Agent requires the Cloudhub Admin right. Apply this setting to each environment.
Cloudhub Admin is required
To enable monitoring of the Anypoint instance, apply the Cloudhub Admin right to each environment.

What Mule ESB User rights does the Nodinite Mule ESB Monitoring agent require?

This section is applicable for version 3.x.

The Nodinite Mule Monitoring Application (Zip file) needs to be installed into the Mule ESB server instance (repeat for each node to be monitored)

What Firewall settings does the Nodinite Mule ESB Monitoring agent require?

The Mule ESB Monitoring Agent has both inbound and outbound TCP-based communication:

  1. Between the Monitoring Service and the Mule ESB Monitoring Agent
  2. For version 3.x, between the Mule ESB Monitoring Agent and instances with the Nodinite Mule ESB Monitoring Application (install ZIP file)

The agent can be installed On-Premise using TCP/IP and/or in the Cloud using Service Bus Relaying (see also the external link for additional information 'Azure Relay FAQs').

graph LR subgraph "Nodinite Instance" roMonitoringService(fal:fa-watch-fitness Monitoring Service) roNI(fal:fa-monitor-waveform Mule ESB Monitoring agent) roMonitoringService --> |8000/443| roNI end subgraph "Mule ESB (v3.x)" roSQLDB(fal:fa-random Instances with Nodinite Mule ESB Monitoring Application) roNI --> |8084, ...| roSQLDB end subgraph "CloudHub (v4.x)" roNI --> |443| roCH(fal:fa-cloud-arrow-up Anypoint CloudHub platform) end

1. Between the Monitoring Service and the Mule ESB Monitoring Agent

The following ports must be allowed on the Windows server where the agent is installed and running :

Port Name Inbound Outbound TCP UDP Nodinite Version Comment
53 DNS All The Agent needs to know where your other servers/services are (can sometimes optionally be solved using entries in the local hosts´ file)
443 TCP - - All eu1.anypoint.mulesoft.com
443 TCP - - All anypoint.mulesoft.com

Option 1a (Nodinite v7 - IIS hosted on local network)

Port Name Inbound Outbound TCP UDP Nodinite Version Comment
Custom HTTP/HTTPS v7 Agent IIS site port (configured during installation in the Portal). Only required if agent is on a remote IIS server

Note

Nodinite v7 IIS Hosting: When agents are hosted in IIS on the same server as the Nodinite application (typical installation), firewall rules are not required between the Monitoring Service and the agent. The custom port is assigned during installation via the Nodinite Portal and only needs to be opened if the agent is hosted on a remote IIS Windows Server.

Option 1b (Nodinite v6 and earlier - Windows Service on local network)

Port Name Inbound Outbound TCP UDP Nodinite Version Comment
8000 RPC v6 and earlier Communication is initiated by the Monitoring Service. Only used with legacy MSI installer on remote Windows servers

Note

Nodinite v6 Legacy: Port 8000 is only used when agents have default installations on remote Windows servers using the legacy MSI installer. This port is not required for Nodinite v7 IIS-hosted agents.

Option 2 (Cloud/Hybrid - All versions)

Use Service Bus Relayed connections when Nodinite and the agent are on totally different networks.

Nodinite uses the same principle technique as the On-Premise data gateway, see 'Adjust communication settings for the on-premises data gateway' user guide.

Port Name Inbound Outbound TCP UDP Nodinite Version Comment
443 HTTPS All Secure outbound traffic
5671, 5672 Secure AMQP All
9350 - 9354 Net.TCP All

2. Between the Mule ESB Monitoring Agent and Mule ESB Instances (v3.x)

Server types: Agent Server (Mule ESB Monitoring Agent), Mule Server (on-premise Mule ESB v3.x runtime with Nodinite Mule ESB Monitoring Application installed).

This section is applicable for Mule ESB version 3.x only.

Mule Monitoring Application Connection (Agent → Mule ESB v3.x)

The agent connects to on-premise Mule ESB v3.x instances with the Nodinite Mule ESB Monitoring Application (installed via ZIP file) to collect monitoring data.

Direction Source Destination Protocol Port(s) Purpose Notes
Outbound Agent Server Mule Server (v3.x) TCP 8084 Mule Monitoring Application Default port for monitoring data collection
Inbound Mule Server (v3.x) Agent Server TCP 8084 Response traffic Allowed automatically by stateful firewalls

Tip

Custom Port Configuration: The default port 8084 can be customized during installation of the Nodinite Mule ESB Monitoring Application. Only make changes to this value after consulting Nodinite support.

Tip

Multiple Mule Instances: If monitoring multiple Mule ESB v3.x instances, ensure the Agent Server has outbound connectivity to all configured Mule servers on port 8084 (or custom ports).

3. Between the Mule ESB Monitoring Agent and Cloudhub Platform (v4.x)

Server types: Agent Server (Mule ESB Monitoring Agent), Cloudhub Cloud (MuleSoft Anypoint Cloudhub platform).

This section is applicable for Mule ESB version 4.x and Cloudhub-hosted applications.

Cloudhub API Connection (Agent → Cloudhub Platform)

The agent connects to the MuleSoft Anypoint Cloudhub platform to monitor cloud-hosted Mule ESB v4.x applications.

Direction Source Destination Protocol Port(s) Purpose Notes
Outbound Agent Server Cloudhub Cloud (anypoint.mulesoft.com) TCP 443 (HTTPS) Cloudhub platform API Monitor cloud-hosted Mule applications
Outbound Agent Server Cloudhub Cloud (eu1.anypoint.mulesoft.com) TCP 443 (HTTPS) Cloudhub EU region For EU-hosted applications
Inbound Cloudhub Cloud Agent Server TCP 443 (HTTPS) Response traffic Allowed automatically by stateful firewalls

Tip

Cloudhub Authentication: The agent requires Cloudhub Admin rights for each environment to be monitored. Apply this setting in the Anypoint platform for each environment. See Mule ESB Monitoring Agent for configuration details.

Tip

Regional Endpoints: Ensure the Agent Server can reach the appropriate Cloudhub regional endpoints:

  • anypoint.mulesoft.com (US region - default)
  • eu1.anypoint.mulesoft.com (EU region)

Configure firewall rules based on your Cloudhub deployment region.

Note

No Inbound Rules on Cloudhub: MuleSoft Cloudhub is a cloud service accessed outbound from the Agent Server. No inbound firewall rules are required on the Cloudhub side.

Note

DNS Resolution: All servers (Agent Server and Mule Servers) require outbound access to DNS on TCP/UDP port 53 for name resolution. This is already listed in section 1 and applies universally. You can optionally solve this using entries in the local hosts file on each server.

Important

Stateful Firewalls: Most modern Windows Firewall implementations are stateful, meaning inbound response traffic for established outbound connections is automatically allowed. The inbound rules listed above are primarily for reference and troubleshooting scenarios where stateful inspection may be disabled or restricted.

Next Step

Install Mule Monitoring Agent

Add or manage a Monitoring Agent Configuration
Monitoring
Administration