Enable Monitoring for JVM Crashes

Before you can monitor JVM crashes, you must:
  • Install and enable a Machine Agent on the machine you want to monitor for JVM crashes. JVM Crash Guard works with the Machine Agent to trigger a policy when a JVM Crash event occurs.
  • Ensure that the Machine Agent is running with the required privileges:
    • On Windows, the Machine Agent must run in Administrator root mode.
    • On Linux, JVM Crash Guard requires that the Machine Agent user be able to read all the processes in /proc/* . This may be the root user or another user with this privilege.
  • Enable the JVM Crash Guard (it is disabled by default). Navigate to extensions/CrashGuard/conf/crashGuardConfig.yml and open the crashGuardConfig.yml file. Set enabled to true.
Note: If an uninstrumented JVM crash occurs within less than a minute of a previous crash, it will not be reported by the Machine Agent. In some circumstances, the JVM may crash and then be restarted only to crash again within one minute. For this repetitive cycle crash and restart scenario, only the first JVM crash is reported by the agent.
Once you have verified the requirements, follow these steps to create a policy for JVM crash events:
  1. From the left-hand navigation menu, click Alert & Respond > Policies > Create a Policy.
  2. In the Other Events section, expand the Server Crashes option and click JVM Crash.
    The JVM Crash event then becomes a trigger to fire a policy.
  3. Proceed as usual to create the policy.
    See Policies.