Ignore Exceptions and Log Messages as Error Indicators

Certain types of exceptions, loggers or log messages as transaction error indicators may not reflect events that should be counted as transaction errors in your environment. They may include exceptions raised by application framework code or by user login failures.

When you configure an exception to be ignored, the agent detects the exception, increments the exception count, and displays the exception in Exceptions lists in the UI, but the business transaction in which the error is thrown is not considered an "error transaction" for monitoring purposes. The transaction snapshot would not show the exception in the Summary or Error Details section and the user experience for the transaction instance would be unaffected by the exception.

To configure exceptions for the agent to ignore, click the Add New Exception to Ignore button in the error configuration window.

Enter the name of the exception to be ignored. The name must be the same as the name displayed in Name column given in Troubleshoot > Errors > Exceptions. For example, in the screenshot below, you would enter PostgresException to ignore this exception.

Note: The text field for Match Condition for Exception Message cannot contain the characters ", <, >, and &.

The following example directs the agent to ignore java.lang.RuntimeExceptions that wrap a javax.sql.SQLException only when the exception.getMessage() call in the root exception contains the string "format". (Other types of java.lang.Runtime exceptions will not be ignored.)

When you define the class of an exception to ignore by an exception chain, the exception message against which the match condition is applied must be in the root exception of the chain. The match is not applied to any nested exceptions.

In .NET and Java, you can specify that errors logged with certain loggers or logger categories be ignored. Click Add New Category/Logger to Ignore.

Also, you can select an existing detect/ignore configuration to enable the Configure Business Transaction option. 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
Note: Only the selected configuration is applied to the business transaction. All the other application-level configurations are not applied to the business transaction.