AppDynamics Application Intelligence Platform

3.8.x Documentation

PDFs

Videos

Release Notes

Skip to end of metadata
Go to start of metadata

Identifying and troubleshooting errors in your application.

Error Transactions and Exceptions

An error transaction is a business transaction that experienced an error during the transaction execution. The error can be:

  • A runtime error reported by the PHP server and captured by the agent. These include Fatal Errors, Warning and Notices thrown by the PHP runtime. These types of errors do not provide a stack trace.
  • Certain exceptions thrown by the application. These include unhandled exceptions (when an exception is thrown and there is no try block) and handled exceptions during an exit call (when there is a try block during an exit call). These types of errors do provide a stack trace.

If a transaction experiences an error, it is counted as an error transaction and not as a slow, very slow or stalled transaction even if the transaction was also slow or stalled.

There is not a one-to-one correspondence between the number of errors and the number of exceptions. For example, a business transaction may experience a single code 500 error in which several exceptions were logged as the transaction passed through multiple tiers.

You can configure the types of errors that AppDynamics detects as well as the types of exceptions to ignore. See Configure Error Detection for PHP.

 
 

To Troubleshoot Error Transactions

1. Click Troubleshoot -> Errors in the left navigation panel.

The error viewer opens.

2. Click the Error Transactions tab if it is not already selected.

3. From the time range drop-down menu select the time range for which you want to view information about error transactions.

A graph of the error transactions displays at the top of the viewer. You can get an exact count of the errors per minute at a particular point in time by hovering with your pointing device on the line in the graph.

To the right of the graph is a summary of the load and the error transactions.

Check the Plot check box if you want the graph at the top of the viewer to show the load over the selected time period. Clear this check box if you want the graph to show only the error transactions.

4. The error transaction snapshots are listed in the lower part of the viewer. To filter this list click Show Filters and select the filter criteria.

5. To examine the root cause of an error, select the snapshot from the list and click View Transaction Snapshot. See Transaction Snapshots for information about examining snapshots.

6. To identify the most expensive calls or queries, select a snapshot from the list and click Analyze and then click Identify the most expensive calls / SQL statements in a group of snapshots.

The Most Expensive Methods / SQL Statements viewer opens.

7. In the lower panel click the Expensive Methods tab to view the methods with their total and average execution times and call counts. Click the  Expensive SQL tab to view the queries with their counts and execution times.

To Troubleshoot Exceptions

1. Click Troubleshoot -> Errors in the left navigation panel.

2. Click the Exceptions tab if it is not already selected.

The total exception count, HTTP Error Codes and Error Page Redirects for the selected time range are reported in the upper panel. You can get an exact count of the exceptions per minute at a particular point in time by hovering with your pointing device on the line in the graphs.

The exceptions list is displayed in the lower panel.

  • To filter the exception list, enter the filter term in the filter text field.
  • To see only exceptions with performance data, clear the Show Exceptions with 0 count checkbox.

3. To view details of a particular exception, select the exception the list in the lower panel and click View Details.

4. To view transaction snapshots for an exception:

a. In the exception detail window, click the Occurrences of this Exception subtab.

b. Select a snapshot from the list.

c. Click View Details.

d. In the snapshot flow map that displays, click Drill Down to get the details of the snapshot. See Transaction Snapshots.

5. To view a stack trace for an exception:

a. In the exception detail window, click the Stack Traces for this Exception tab.

b. Click an exception in the left panel.

The right panel displays the stack trace for the selected exception.

Learn More