Method Analysis of Debugging Diagnosis Does Not Support Drilldown for Nested Calls of Method Overloading

Symptom

1. Log in to the APM console.
2. Click on the left and choose Management & Governance > Application Performance Management.
3. In the navigation pane, choose Application Monitoring > Metrics.
4. In the tree on the left, click next to the target environment.
5. Click the Debugging Diagnosis tab.
6. Click Method Analysis. The Method Analysis page is displayed.
7. Enter class name com.example.hello.helloController, select method name boy, and click Confirm.
8. Click Drill Down corresponding to org.apache.http.impl.client.CloseableHttpClient.execute #-1.

9. Click Drill Down corresponding to org.apache.http.impl.client.CloseableHttpClient.execute #108. The system does not respond.

Trigger Conditions

When method overloading exists (that is, multiple functions with the same name exist in the class and nested calls exists), only the first called method can be traced. That means if the system calls an execute method and then calls its nested execute method, the nested method cannot be drilled down.

Root Cause and Constraint

The watch and trace commands in the frontend do not specify overload method parameters. Therefore, accurate method information cannot be returned during debugging diagnosis. Only the information about the first method is returned. If a nested execute method is called, its information cannot be returned.

Debugging diagnosis does not support drilldown for nested overloaded methods.