- 2 minutes to read
What happens if the Monitoring Agent service stops?
WSO2 keeps running; only the monitoring pauses. Nodinite monitors WSO2 with the JMX Monitoring Agent, which only reads CPU and heap values from the WSO2 JVM over JMX. Nothing in WSO2 depends on the agent.
The Parts That Can Stop
The JMX Monitoring Agent has two parts on the Agent Server (Prerequisites):
- the JMX Monitoring Agent, an IIS-hosted web application that the Monitoring Service polls
- the Spring Boot JMX Gateway, a Java application that NSSM runs as a Windows Service and that connects to each JVM over JMX
If either part stops, or the network between them and WSO2 fails, the agent can't deliver new values. The Monitoring Service notices that it can't get an answer, and the WSO2 Resources stop reflecting the real state of the JVMs until the agent and gateway work again. Problems that start and end entirely during this monitoring gap aren't reported afterward.
Reduce the Risk
- Set the Windows Service for the Spring Boot JMX Gateway to start automatically, and let NSSM restart it on failure.
- Monitor the Agent Server itself, for example the gateway's Windows Service and IIS, with the Windows Server Monitoring Agent.
- Connect the Monitor View that holds the WSO2 Resources to Alarm Plugins, so a lost connection to the agent reaches someone.