- 2 minutes to read

How quickly does Nodinite detect when a WSO2 service stops?

Within 2 minutes—30-second polling interval plus processing time. This FAQ explains the detection speed of the Nodinite monitoring agent for a service stopped event on WSO2.

Alert Timeline

The following alert timeline shows a typical sequence:

  • 2:00:00 AM — The WSO2 service stopped.
  • 2:00:30 AM — The monitoring agent polls the next cycle.
  • 2:00:30 AM — JMX or the Micro Integrator Management API reports the stopped state.
  • 2:00:40 AM — Alerting rules finish processing.
  • 2:00:40 AM — PagerDuty receives the notification.
  • 2:00:45 AM — The on-call engineer is paged.

Total detection speed: about 45 seconds from a service stopped event to a PagerDuty page.

Polling Interval

The default polling interval is 30 seconds, and you can configure the monitoring agent to use values between 15 and 120 seconds. A shorter polling interval improves detection speed but increases the number of management calls to WSO2.

What Affects Detection Speed

Detection speed also depends on alerting rules, notification transport, and whether the agent reads state by using JMX for WSO2 Enterprise Integrator or the Management API for Micro Integrator.

Next Steps

  • Alarm Plugins — Route alerting to PagerDuty, email, Teams, or a webhook target.
  • Overview — Review the polling model and monitored WSO2 resources.