How quickly does Nodinite detect when a WSO2 service stops?
Within 2 minutes—30-second polling interval + processing time. Agent checks WSO2 server status every 30 seconds (configurable 15-120 seconds), detects service stopped, processes alert rules (~10 seconds), sends notification. Alert timeline: Service crashes at 2:00:00 AM → Agent checks at 2:00:30 AM (next poll cycle) → Detects stopped status via JMX/MI API → Processes alert rule (evaluates conditions, matches destination) → PagerDuty API call → Notification sent 2:00:40 AM → On-call engineer paged 2:00:45 AM (phone alert). Total: 45 seconds from service crash to engineer paged. Faster detection: reduce polling interval to 15 seconds (increases CPU load on agent server slightly—from 2% to 4% CPU typically).
Related Questions
See all FAQs: [Troubleshooting Overview][]