When the app agent doesn't automatically discover an entry point for a framework in your application, you can use Uninstrumented Code detection to find entry points for the framework. After you identify an entry point you want to track as a business transaction, you can create a custom match rule.

Uninstrumented Code detection identifies the support exit calls for an app agent on the node when the entry point is undetected. In the following example the Java Agent discovers some uninstrumented JDBC exit points:

You can select an exit point and clickView Stack Traceto display the call stack for the exit point. Select any call in the stack trace and clickMonitorto show interactive data for that specific call. When the agent returns the monitoring result, you can inspect the values for a specific method invocation including theInvoked Object,Return Value,Parameters, and more.

The example below shows the upstream stack trace for the com.mysql.jdbc.PreparedStatement:executeQuery JDBC exit call.

When you identify the method you want to instrument, you can click to add a POJO or POCO. The Controller UI automatically populates the Rule Configuration in the Add Rule editor with the class and method you want to instrument. Complete the custom match rule for the POJO or POCOas normal.