- 2 minutes to read

How quickly does Nodinite detect when a Mule application stops?

Within 2 minutes—30-second polling interval plus processing time.

The Nodinite Mule ESB Monitoring Agent checks MuleSoft Anypoint and Mule ESB server status every 30 seconds (configurable). The detection speed depends on the polling interval—when an application stops, the agent detects it on the next poll cycle and sends notifications. The monitoring flow raises alerts as soon as the next poll completes. This page is part of the Troubleshooting guide.

Alert Timeline Example

The following example shows the detection time and notification sequence after an application stopped:

  • 3:00:00 AM – Application crashes
  • 3:00:30 AM – Agent polls at next cycle, detects stopped status
  • 3:00:40 AM – Processes alert rule (~10 seconds)
  • 3:00:40 AM – PagerDuty notification sent
  • 3:00:45 AM – On-call engineer paged

Total detection speed: ~45 seconds from application stopped to PagerDuty page.

Configuring the Polling Interval

To adjust detection speed, configure the polling interval in the Configuration Guide:

  • Default polling interval: 30 seconds
  • Faster detection: 15-second polling interval (slightly increases load on Mule server)

Tip

Reducing the polling interval improves detection speed but increases the number of API calls to the Mule server. Test in a non-production environment before applying to production.

Note

The polling interval setting is configured in the Settings tab of the Configuration Guide.

Next Step

Configuration Guide

Mule ESB Monitoring Agent Overview All FAQs FAQ - Agent Service Failure FAQ - Restart Without MMC