- 2 minutes to read

What happens if the Monitoring Agent service stops?

No impact on WSO2 servers—monitoring is read-only. This FAQ explains what changes when the Monitoring Agent service stops and how to reduce a monitoring gap.

No Impact on WSO2

A Monitoring Agent crash, restart, or service stop does not affect WSO2 runtimes. The agent reads status data and only performs Remote Actions when a user explicitly requests one.

Monitoring Gap

During a monitoring gap, alerting pauses. That gap can come from a service stop, a server reboot, or a network outage between the agent and WSO2. If a resource fails during that gap, the agent cannot send an alert until connectivity returns.

Restart Behavior

When the agent starts again, it reads the current state of every monitored WSO2 resource. It can then alert on resources that are currently stopped, but it does not replay historical events that happened entirely during the outage window.

High-Availability

High-availability reduces risk. If you deploy two Monitoring Agent instances for the same WSO2 estate, one agent can continue alerting when the other has a problem.

Next Steps

  • POC — Test high-availability and failover for the Monitoring Agent.
  • Alarm Plugins — Review alerting destinations and escalation rules.