All transaction errors that have been detected according to the configured error detection rules in the selected time frame of the Controller UI appear in the Error Transactions tabs of the Errors page.

By default, Splunk AppDynamics considers a business transaction to be in error if it detects one of the following types of events in the context of the transaction:

• An unhandled exception or error. An exception that is thrown and never caught or caught after the business transaction terminates results in a transaction error, and the exception is presented in Splunk AppDynamics. An exception that is thrown and caught within the context of the business transaction is not considered a transaction error and the exception is not captured in Splunk AppDynamics.
• An exception caught in an exit call, such as a web service or database call.
• An HTTP error response, such as a status code 404 or 500 response.

• A custom-configured error method and error message.

Error detection configuration is described in Error Detection.

Errors that occur on a downstream tier that are not propagated to the originating tier do not result in a business transaction error. If the originating client receives a 200 success response, for example, the business transaction is not considered an error. The error contained within the downstream tier does count against the Error Per Minute metric for the continuing segment.

When a business transaction experiences an error, it is counted only as an error transaction. It is not also counted as a slow, very slow or stalled transaction, even if the transaction was also slow or stalled.