The Plumbr Agent monitors the creation of Exceptions during a transaction. Whenever a transaction is flagged as failed, the chronologically last Exception is linked to the transaction as a root cause. The Exception contains the full stack trace, allowing you to zoom in to the source code and quickly fix the underlying error.
Exceptions that do not affect any transactions or exceptions used to steer control flow are not exposed. Exceptions are grouped together into root causes by Exception class, so for example all ArrayIndexOutOfBoundExceptions would be grouped together as instances of a single root cause. Different call stacks are visible from the root cause details to verify whether or not the source code would need patches in multiple locations.