Catched library exception still marked as Exception in APM UI


Is it normal that catched Exceptions in a Library are still shown as Errors in the APM UI. I could not find any relevant documentation about when/how Exceptions are sent by the APM Java agent.


In this case it's the following code that throws the Exception but it is caught in the same method body.

How does the agent determine the Java exceptions to send to the APM server? I know about ignore_exceptions but unfortunately in this case an IOException is thrown which is too generic to ignore.

Best regards,

My colleague Sylvain has a nice explanation. I think you would need to exclude process from the instrumentation to avoid this one

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.