Detect HTTP Responses or Redirect Pages as Errors

In Java, .NET, Node.js, Python, and Web Server you can configure errors based on HTTP response codes. If the error code is set as part of business transaction processing, the transaction is marked as an error. For PHP, it is possible to classify transactions as in error based on 4xx HTTP return codes using the PHP Agent Configuration Settings.

By default, Splunk AppDynamics captures HTTP error codes from 400 to 505. HTTP response codes may convey errors that occur at the business level of an application. For example, in an e-commerce application, a 522 error might indicate that an item is out of stock. For this case, you may want to include the error as a default transaction error indicator.

To exclude a return code add them to the error detection list by creating a custom error code range and then disabling that error code by clearing itsEnabledcheckbox. This in effect excludes the error code as an error indicator.

For Java and .NET agents, you can specify custom redirect target error pages as error indicators. To specify a redirect page, click AcmeErrorPage.jspAdd Error Redirect Pageand add a name for the configuration and a regular expression to match the URL of the page, such as

Also, you can select an existing detect/ignore configuration to enable theConfigure Business Transactionoption. You can use this option to associate the following events with a specific business transaction.

• Custom Logger
• Ignore exception, message, and logger
• HTTP return code and redirect page