- 2 minutes to read

What happens if the Monitoring Agent service stops?

The Nodinite Mule ESB Monitoring Agent is a read-only observer—it does not control Mule ESB runtimes. Understanding the impact of an agent service stoppage helps you plan your monitoring strategy and high-availability configuration. This page is part of the Troubleshooting guide.

Impact on Mule Runtimes

The agent reads JMX data and REST API endpoints to observe MuleSoft application states. If the agent crashes or restarts:

  • Monitored Mule applications continue running normally
  • The agent does not control runtimes unless a Remote Action was explicitly sent
  • No configurations or application states are modified

Monitoring Gap During Agent Downtime

During agent downtime, status checks pause:

  • No alerts are sent if applications stop during this window
  • When the agent restarts, it resumes monitoring immediately
  • The agent catches up on current state—it does not replay history

Important

If a Mule application stops while the Monitoring Agent is experiencing agent downtime, you will not receive an alerts for that event. The agent will detect the stopped state on its next polling cycle after restart.

High-Availability Configuration

For mission-critical environments, deploy two agents monitoring the same Mule ESB instances:

  • If Agent 1 stops, Agent 2 continues alerting without interruption
  • Configure alert de-duplication in your alarm plugin to prevent double-notifications
  • Both agents can share the same Monitor Views and alert rules

Tip

High-availability agent deployment is recommended for production environments where monitoring continuity is required 24/7. This ensures you always receive alerts even during Monitoring Agent maintenance windows.

Next Step

Configuration Guide

Mule ESB Monitoring Agent Overview All FAQs FAQ - Restart Without MMC FAQ - Required Permissions