No stack traces

For performance reasons, we cap error reporting as follows:

• 100 events per minute per agent instance
• 20 trace details per minute per agent instance

Our APM agents automatically report errors for unhandled exceptions. In situations where application logic handles the error, our APM agent may miss the error, and won't report a stack trace.

You can use the notice_error() agent-specific API to record handled exceptions.

If you configured errors to be ignored, the stack trace won't be avilable

Returning a 500 error means that the application server itself detected an error and set the HTTPS 500 status code.

• If the error condition was detected and handled by application logic, there was no exception object and thus, no stack.

• If there was an exception object at some point, but it was handled internally by the application code that set the 500 status on the response, then the exception never became visible to the agent. There is no stack available for the agent to report.

  When stack traces are reported, the error results from an exception that was not caught and handled within the application server logic. The agent sees the unhandled exception during a monitored transaction, so it reports the stack trace.

When an error is thrown in a rapidly repeated sequence, the Java compiler may optimize the stack trace away to help performance. To disable this optimization: In your JVM flags, include:

-XX:-OmitStackTraceInFastThrow