- 5 minutes to read

Release Notes

Configuring the Mule ESB/MuleSoft Anypoint Monitoring Agent

Take control of your integration landscape with the Nodinite Mule ESB Monitoring Agent. This guide empowers you to configure and optimize monitoring for both Mule ESB and MuleSoft Anypoint, ensuring visibility, compliance, and operational excellence.

✅ Nodinite supports both Version 3 and 4, on-premise and in the cloud.

Note

Monitoring and remote configuration become available after you install and create the initial Monitoring Agent Configuration for the Mule ESB Monitoring Agent. If this is your first time, start here.

Remote Configuration

As a Nodinite Administrator, click the 'Configuration' button to open a modal and configure the agent:

Remote Configuration
Click the 'Configuration' button to open the configuration modal.

You can adjust configurations on the Resource using the Action button if the Monitor View has the Remote Actions feature enabled.

Adding the Mule ESB/MuleSoft 3.x instance

The Mule ESB/MuleSoft 3.x tab lets you manage one or more server instances.
Click the Add button to add a Mule Server Instance to monitor.
image-add-mule-server
Add your Mule ESB/MuleSoft 3.x instance to monitor.

Configuring the Mule ESB/MuleSoft 3.x instance

image-added-mule-server
Configure your Mule ESB/MuleSoft 3.x instance.

Click the Accordion to expand the selected configuration:
image-edit-mule-server
Expand the configuration for more options.

  • Name: Enter a unique, user-friendly name for your Mule instance
  • Address: Specify the address (including port, default 8084) to the API for the Mule ESB server Application for Nodinite
http://localhost:8084/Nodinite/api

Example address for the Mule ESB/MuleSoft 3.x application (installed using the ZIP file for Nodinite).

Repeat this step for each Mule ESB/MuleSoft 3.x Server instance you want to monitor with Nodinite.

Adding the MuleSoft 4.x instance

The MuleSoft 4.x tab lets you manage one or more server instances.
Click the Add button to add a Mule Server Instance to monitor.
image-add-mule-server
Add your MuleSoft 4.x instance to monitor.

Configuring the MuleSoft 4.x instance

image-added-mule-server
Configure your MuleSoft 4.x instance.

Click the Accordion to expand the selected configuration.

  • Name: Enter a unique, user-friendly name for your Mule instance
  • Organization Id: The Anypoint platform Organization Id
    image-edit-mule-server
    Enter your Anypoint platform credentials.

AnyPoint Environment: Click the Accordion to expand.

  • Environment: The specific environment within Anypoint platform
  • Environment Id: The environment Id for the selected Anypoint platform environment

Mule 4.x Environment configuration
Example of the environment configuration for MuleSoft 4.x.

Authentication for MuleSoft 4.x

The Authentication tab provides two options for securing your connection to Anypoint Platform:

Basic Authentication

Use your Anypoint Platform credentials for standard authentication:

  • Use CloudHub 2.0: Enable this option if using CloudHub 2.0 for authentication
  • Username: Your Anypoint Platform username
  • Password: Your Anypoint Platform password

Mule 4.x Basic Authentication configuration
Example of basic authentication configuration for MuleSoft 4.x with username and password.

Connected Apps Authentication

Use Connected Apps for OAuth2-based authentication (recommended for enhanced security):

  • Use Connected Apps: Enable this option to use a registered Connected App for authentication
  • Client ID: The client ID from your Anypoint Platform Connected App
  • Client Secret: The client secret from your Anypoint Platform Connected App

Proxy Settings

If your environment requires a proxy server to connect to Anypoint Platform:

  • Proxy URL: The URL of your proxy server (e.g., http://proxy.company.com)
  • Proxy Port: The port number for the proxy server (default: 80)
  • User name: The username for proxy authentication (if required)
  • Password: The password for proxy authentication (if required)

Mule 4.x Connected Apps and Proxy configuration
Example of Connected Apps and proxy configuration for enhanced security and network flexibility.

Repeat this step for each Mule 4.x Server instance you want to monitor with Nodinite.

Settings tab

Within the Settings tab, provide details that determine the operation of the Mule ESB Monitoring Agent.
Settings Tab
Settings tab for advanced configuration.

Environment

Set the name of the target environment (e.g., TEST, QA, PROD)—a common feature for all Monitoring Agents.

Debug

Enable or disable the Debug flag for additional file logging as needed. Default is unchecked.

Culture Information

The Culture Information setting determines how time-based data from this agent is presented in the Web Client/Web API.

AI Diagnostics

New 7.4.0

AI Diagnostics (Preview in Nodinite v7.4.0) enables intelligent, autonomous error analysis and remediation recommendations. Available for agents running on .NET 10 with AI Diagnostics enabled.

Configure AI Diagnostics settings:

  • Provider: Select your AI provider:

    • Azure OpenAI - Use Azure's hosted GPT models
    • OpenAI - Direct OpenAI API integration
    • Ollama - Local, privacy-first LLM
    • GitHub Models - GitHub's AI model marketplace

  • Scan Interval: How frequently the agent scans for errors (minutes)

  • Max Tokens: Maximum response length from the AI model

  • Temperature: AI creativity level (0.0 = deterministic, 1.0 = creative)

  • Log File Options: Enable/disable detailed diagnostic logging

See AI Diagnostics for complete configuration and privacy details.

Click 'Save' or 'Save and close' to persist your changes. The new settings/thresholds are evaluated on the next synchronization.
Save and Close buttons
Example of the Save options.

Note

The delay in presenting the new evaluated state depends on the synchronization interval set for the monitoring agent. Click the Sync Now button to force an immediate synchronization.

Save and close: Save and close the dialogue.
Cancel: Close the dialogue without saving changes.

Add Mule ESB Monitoring Agent Configuration

After successfully installing the Nodinite Mule ESB Monitoring Agent, provide connection details so the Monitoring Service recognizes the new agent.

No monitoring or configuration of the Mule ESB Monitoring Agent can be performed before completing the steps below.

Configuration Steps

  1. Add and configure a new Monitoring Agent Configuration

    Connection information is available in the README.txt file in the installation folder

  2. Use the Remote Configuration feature to configure the agent (see the beginning of this guide).
  3. Create one or more self-service enabled Monitor Views that include the selected Resources provided by the Mule ESB Monitoring Agent according to business needs.
  4. Fine-tune specific settings directly on Resources using Remote Actions.

Next Step

Add or manage a Monitoring Agent Configuration
Add or manage Monitor View

Applications
Install Mule Monitoring Agent
Monitoring Agents