What are Root Causes?

When a transaction is flagged as slow or failed, Plumbr looks for the root cause of the underlying issue. Plumbr is able to explicitly track the problematic transactions to the actual root cause in the source code or configuration.

The root cause detection works only in server-side, meaning that only accounts with Plumbr Java Agents will benefit from the root cause detection.

To be able to detect the root causes for slow transactions, Plumbr monitors the JVM for various performance issues. Whenever a particular issue contributes more than 1,000ms to the transaction duration, Plumbr links such issues to the transaction as a root cause.

To detect root causes for failed transactions, Plumbr is capturing all the exceptions thrown while the transaction was being executed. When such an exception is been detected in context of a failed transaction it will be linked to the transaction as the root cause. An example of such a root cause being linked to a transaction is a NullPointerException being triggered during a particular transaction aborting the normal flow of operations and returning a 500-series error to the end user instead.