Errors detected in JVM

If Plumbr Java Agent is used to monitor the server-side of an application, the creation of Java Exceptions is used to more specifically pinpoint the errors. Whenever a user interaction is flagged as failed, the chronologically last Exception occurring is linked to the interaction as an error. The Exception contains the full stack trace, allowing you to zoom in to the source code. Exceptions that do not affect any user interactions / API calls or exceptions used to steer control flow are not exposed.

Exceptions are grouped together into errors by deepest nested Exception class name and a top non-JDK calling method of this exception stacktrace. For example, all NullPointerException thrown by com.mybusiness.finance.Biller.billCustomer would be grouped together as instances of a single error under NullPointerException at com.mybusiness.finance.Biller.billCustomer. If NullPointerException is thrown from different method in code, it’s grouped accordingly.

Different call stacks are visible from the error details to verify whether or not the source code would need patches in multiple locations.