Monitoring MuleSoft 4

Proactively monitor your MuleSoft 4 Anypoint platform with the Nodinite Mule ESB Monitoring Agent. Get instant alerts, actionable insights, and remote control to keep your integration landscape healthy and compliant.

This guide explains what Nodinite monitors, how it translates MuleSoft states into meaningful monitoring, and how you can use remote actions to resolve issues quickly. For hands-on management, see Managing Mule 4.x.

Features

• Automatic Discovery
  • The Nodinite MuleSoft agents leverage the MuleSoft REST API'S to automatically discover your Mule Apps. Granting access to any Mule App is easy with Monitor Views.
• State Evaluation
  • Ensure your Mule Apps always run as intended! Get alerts if anyone disables a flow or if an app stops unexpectedly.

    If Nodinite can't check the state of your MuleSoft Apps, chances are no one else can use them either.

• Category-based Monitoring
  • Nodinite groups monitored Resources by Categories for clarity and control.
    
    List of categories being monitored.

State evaluation for Mule Resources

The Mule ESB Monitoring Agent for Nodinite provides detailed information and remote actions for MuleSoft 4.x resources. Supported Mule Categories:

• Application
• Flow
• Server

Application

List of Mule Apps in a Monitor View.

Nodinite displays each Mule App as a Resource. For example, 42 deployed Mule Apps become 42 Resources categorized as Mule Application, regardless of flow or server count.

• The [Resource][] name comes from the deployed Mule App, prefixed by the deployment target.
• All Mule Apps belong to the 'Mule Application' category.
• The Application name is based on deployment paths, ensuring uniqueness:
  • Configuration name/environment name/target name/mule app name

Here's an example of Application naming pattern.

Each Mule App (as a Resource) has one of the following evaluated states at any moment:

	State	Status	Description	Actions
	Unavailable	Resource not available	If the Mule App can't be evaluated due to network or deployment problems	Review Prerequisites
	Error	Application is not running	Mule App is stopped/undeployed or not running; there are failed runs	Start mule application
	Warning	Application in transition state	Mule App is starting, stopping, or undeploying
	OK	Running and accepting requests	Mule app is running and/or there are no failed runs

You can reconfigure state evaluation on each Resource using the Expected State feature.

Flow

List of Mule Flows in a Nodinite Monitor View.

Nodinite displays each Mule flow as a Resource. For example, 20 deployed flows become 20 Resources categorized as Mule Flow.

• The [Resource][] name comes from the Mule flow, prefixed by the application and target name.
• All Mule Flows belong to the 'Mule Flow' category.
• The Flow name is based on deployment paths, ensuring uniqueness:
  • Configuration name/environment name/target name/mule app name/mule flow name

Here's an example of Flow naming pattern

Each Mule Flow (as a Resource) has one of the following evaluated states at any moment:

	State	Status	Description	Actions
	Error	Flow is not running	Mule flow is stopped or not running; there are failed runs	Start mule flow
	Warning	Unmanaged flow	Flow in transition states (App behavior)
	OK	Within user-defined thresholds	Mule app is running and/or there are no failed runs

You can reconfigure state evaluation on each Resource using the Expected State feature.

Server

List of Mule Servers in a Monitor View

Nodinite displays each Mule server as a Resource. For example, 3 added servers become 3 Resources categorized as Mule Server.

• The [Resource][] name comes from the Mule server.
• All Mule Servers belong to the 'Mule Server' category.
• The Server name is based on deployment name, ensuring uniqueness:
  • Configuration name/environment name/target name
    
    Here's an example of Target/Server naming pattern

Each Mule Server (as a Resource) has one of the following evaluated states at any moment:

	State	Status	Description	Actions
	Error	Disconnected	Mule server is stopped or not running; there are failed runs	Start mule server
	Warning	Created/Connected	Server is available but not ready to accept requests
	OK	Running	Mule server is running and accepting requests

You can reconfigure state evaluation on each Resource using the Expected State feature.

Next step

• Managing Mule 4.x

Related Topics

• Prerequisites
• Resources
• Categories
• Applications