Catched library exception still marked as Exception in APM UI

NickWe · June 29, 2023, 1:20pm

Hi,

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.

github.com

apache/tika/blob/main/tika-core/src/main/java/org/apache/tika/parser/external/ExternalParser.java#L154


      
           * something like "myapp --version" to check to see if "myapp"
           * is installed and on the path.
           *
           * @param checkCmd   The check command to run
           * @param errorValue What is considered an error value?
           */
          public static boolean check(String checkCmd, int... errorValue) {
              return check(new String[]{checkCmd}, errorValue);
          }
          
          public static boolean check(String[] checkCmd, int... errorValue) {
              if (errorValue.length == 0) {
                  errorValue = new int[]{127};
              }
          
              Process process = null;
              try {
                  process = Runtime.getRuntime().exec(checkCmd);
                  Thread stdErrSuckerThread = ignoreStream(process.getErrorStream(), false);
                  Thread stdOutSuckerThread = ignoreStream(process.getInputStream(), false);
                  stdErrSuckerThread.join();

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,
Nick

Jack_Shirazi · July 13, 2023, 1:58pm

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

system · August 10, 2023, 1:59pm

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