Cloud Monitor:Exception analysis

Scenarios

ARMS records exceptions only if they propagate outside try-catch blocks. Assume the ARMS agent has instrumented public void methodA and public void methodB, which call each other:

• Scenario 1: Both methods catch exceptions.

      public int methodA() {
          try {
              return methodB();
          } catch (Throwable e) {
              e.printStackTrace();
              return 0;
          }
      }
  
      public int methodB() {
          try {
              return 1 / 0;
          } catch (Throwable e) {
              e.printStackTrace();
              return 0;
          }
      }

  Result: ARMS records no exceptions because they are caught and handled within the try-catch blocks.

• Scenario 2: methodA catches an exception, whereas methodB returns one.

      public int methodA() {
          try {
              return methodB();
          } catch (Throwable e) {
              e.printStackTrace();
              return 0;
          }
      }
  
      public int methodB() {
          return 1 / 0;
      }

  Result: ARMS records one  java.lang.ArithmeticException exception (uncaught in methodB).

• Scenario 3: Both methods return exceptions.

      public int methodA() {    
          return methodB();
      }
  
      public int methodB() {
          return 1 / 0;
      }

  Result: ARMS records two  java.lang.ArithmeticException exceptions.

• Scenario 4: methodA catches methodB’s exception and rethrows it as RuntimeException.

      public static int methodA() {
          try {
              return methodB();
          } catch (Throwable e) {
              throw new RuntimeException(e);
          }
      }
  
      public static int methodB() {
          return 1 / 0;
      }

  Result: ARMS records one java.lang.ArithmeticException exception (uncaught in methodB) and one java.lang.RuntimeException exception (thrown by methodA).

Prerequisite

An agent is installed for the application.

1. Visit the Playground demo environment. By default, you are logged on to the o11y-demo-cn-hangzhou workspace.

2. In the left navigation pane, choose Application Center > Application Observability > Application Monitoring.

View in console

1. Log on to the Cloud Monitor 2.0 console, and select a workspace. In the left navigation pane, choose Application Center > Application Observability > Application Monitoring.

2. On the Applications page, click an application. Then, choose Scenario Analysis > Exception Analysis.

   • In the Quick Filter section, filter the number of exceptions and the exception list by exception name, interface name, application, and instance.

   • In the trend charts section, view the number of exceptions that occurred in a specified time period, with each bar in the chart being stacked by exception name.

   • The exception list shows information such as the name of the abnormal interface, number of exceptions, proportion, and exception summary.

     In the Actions column, you can:

     • Click Overview to view information such as the exception count trend, exception distribution by interface and instance, and exception stack in the panel that appears.

     • Click Traces to view trace details.