Error Configuration for .NET

By default, the Windows .NET Agents can instrument calls using NLog and Log4Net. They can also gather information from System Trace and the Event Log. Beginning with Agents >= 4.5.19 on Linux, and >= 21.2.0 on Windows, Agents running on .NET Core can also instrument calls using loggers that implement the Microsoft.Extensions.Logging.ILogger API. To instrument calls using other loggers, add a custom logger definition. See .

Messages logged as higher than ERROR include severe levels such as CRITICAL or FATAL.

If you donotwant system trace or event log errors to be monitored, disable them by checking the appropriate box. System trace errors are anything written as an error message to the Listeners collection via TraceError.

Event log errors are anything written to the EventLog when the type is set to error. For example:

myEventLog.WriteEntry(myMessage, EventLogEntryType.Error, myID);

Error Configuration for PHP

The PHP Agent instruments the PHP reporting facility. PHP applications can use trigger_error to report errors through that facility. PHP extensions and PHP itself can also use the PHP facility for reporting errors.

By default, the agent can check for PHP errors using multiple thresholds:

• If you select Error, the agent reports only messages and exceptions marked Error.
• If you select Warning, the agent reports only messages and exceptions marked Error and Warning.
• If you select Notice, the agent reports messages and exceptions marked Error, Warning and Notice.

Error Configuration for Node.js

The Node.js Agent reports exceptions thrown by the Node.js application or by Node.js itself.

You can configure certain exceptions or logged messages not to cause transactions to be reported as errors using the ‘Ignored Exceptions’ and ‘Ignored Messages’ lists. See.

Error Configuration for Python Notes

By default, the Python Agent reports error transactions for unhandled exceptions, HTTP status codes greater than or equal to 400, and messages logged at ERROR or higher by the Python logging module.

If you do not want any logged errors to cause transactions to be reported as errors, clear the "Mark Business Transaction as error" checkbox. If you do not want to capture logged messages at all, clear the "Detect Errors" checkbox.

You can configure certain exceptions or logged messages not to cause transactions to be reported as errors using the ‘Ignored Exceptions’ and ‘Ignored Messages’ lists. See.

Error Configuration for Apache Web Server

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.

You can define more error codes as custom error types. Perform the following steps to add an error code:

1. In the Controller UI, open an application and navigate to Configuration > Instrumentation > Error Detection > Web Server.
2. Click Add Code. Provide the error code description and the error code. You can also provide a range of error codes.
3. Click Enable.
4. (Optional) If you want to exclude a custom error code or code range, you can disable that error code by clearing its Enabled checkbox. This excludes the error code as an error indicator.