What happens if the Monitoring Agent service stops?
No impact on WSO2 servers—monitoring is read-only. Agent crash/restart doesn't affect monitored services (agent only reads JMX/MI API data, doesn't control WSO2 unless Remote Action explicitly sent by user). Monitoring gap: During agent downtime (service stopped, server reboot, network outage), status checks pause—no alerts sent if services stop during this window. When agent restarts: resumes monitoring immediately, catches up on current state (queries current status of all services, detects any stopped since last check, sends alerts for currently-stopped services), doesn't replay historical events (gap in uptime logs for downtime period). High-availability: Deploy 2 agents monitoring same WSO2 instances—if Agent 1 stops, Agent 2 continues alerting (configure alert de-duplication: both agents send alerts to same Slack channel/PagerDuty service, PagerDuty merges duplicate incidents automatically).
Related Questions
See all FAQs: [Troubleshooting Overview][]