- 3 minutes to read

Troubleshooting the MuleSoft / Mule ESB / Anypoint platform Monitoring Agent

If you encounter issues you can't resolve, reach out to our Support or email us at support@nodinite.com for expert assistance.

Frequently Asked Questions

Quick answers to common questions about monitoring MuleSoft with Nodinite:

# Question Quick Answer
FAQ1 Can business users view application status without technical knowledge? Yes—Nodinite provides business-friendly dashboards with no technical jargon required.
FAQ2 Can I integrate with existing ticketing systems (ServiceNow, Jira)? Yes—use Alarm Plugins to create tickets automatically when applications fail.
FAQ3 Can I monitor CloudHub-deployed Mule applications? Yes—Nodinite monitors both CloudHub and on-premise (Hybrid) Mule deployments.
FAQ4 Can I monitor Mule Community Edition (free version)? Yes—Nodinite monitors Mule Community Edition using JMX/HTTP endpoints.
FAQ5 Can I restart applications without MMC (Mule Management Console)? Yes—use Remote Actions to restart applications directly from Nodinite.
FAQ6 Do I need Anypoint Runtime Manager license to use Nodinite? No—Nodinite operates independently; you only need credentials to access Mule APIs.
FAQ7 How do I monitor 40+ applications—do I need 40 agent licenses? No—one Monitoring Agent can monitor unlimited Mule applications and servers.
FAQ8 How quickly does Nodinite detect when a Mule application stops? Within seconds—configurable polling intervals detect failures immediately.
FAQ9 What happens if the Monitoring Agent service stops? Historical data remains in Nodinite; monitoring resumes automatically when service restarts.
FAQ10 What permissions does the Monitoring Agent need on Mule servers? Read access to Anypoint APIs and OAuth app credentials with appropriate scopes.
FAQ11 What's the difference between monitoring Mule 3.x vs. 4.x? Minimal—Nodinite supports both versions via Anypoint platform APIs.
FAQ12 Which Mule versions are supported? Mule 3.x, Mule 4.x, CloudHub, and Hybrid deployments.

How do I add MuleSoft Monitoring with Nodinite?

Easily add any number of MuleSoft managers for Nodinite to monitor—just ensure you have the proper access rights. Follow the step-by-step instructions in the Configuration user guide to get started.

Scope the OAUTH Access

To enable the Nodinite Mule ESB Monitoring Agent to operate and interact with resources, you must set the correct scopes for your connected app.

The agent uses the following endpoints:

Hybrid

Hybrid environments require these endpoints and actions:

  1. Get Servers
    • Method: GET
    • Endpoint: /servers
  2. Stop/Restart Server
    • Method: POST
    • Endpoint: servers//actions
    • Data: <json content>
  3. Get Applications
    • Method: GET
    • Endpoint: /applications
  4. Start/Stop Application
    • Method: PATCH
    • Endpoint: applications/
    • Data: <json content>
  5. Application Monitoring
    • Method: GET
    • Endpoint: applications/?from=&to=&detailed=true
  6. Get Flows for Application by ID
    • Method: GET
    • Endpoint: applications//flows
  7. Start/Stop Flow
    • Method: PATCH
    • Endpoint: applications//flows/
    • Data: <json content>
  8. Get Flow
    • Method: GET
    • Endpoint: applications//flows/

Cloud Hub

CloudHub environments require these endpoints and actions:

  1. Get Applications
    • Method: GET
    • Endpoint: /applications
  2. Get Application by Name
    • Method: GET
    • Endpoint: applications/
  3. Start/Stop Application
    • Method: PUT
    • Endpoint: /applications
    • Data: <json content>
  4. Get Application Log (deployments)
    • Method: POST
    • Endpoint: applications//deployments?orderByDate=DESC
    • Data: <json content>

Nodinite delivers robust monitoring and troubleshooting for your MuleSoft landscape, empowering you to resolve issues quickly and maintain operational excellence.