UNINSTRUMENTED CODE DISCOVERY

1 . A system for detecting uninstrumented code in a monitored environment, the system including:

a processor;

a memory; and

one or more modules stored in the memory and executable by a processor to perform operations including:

provide a user interface that displays an interactive dashboard of the monitored environment;

display, through the user interface, a stack trace that includes lines of code that are uninstrumented;

receive a selection of one of the lines of code in the displayed stack trace;

display live introspective data on the selected line of code;

receive input requesting the selected line of code to be instrumented and monitored; and

instrument the requested line of code and removing from display of the lines of code that are uninstrumented.

2 . The system of claim 1 , wherein when displaying the live introspective data, the one or more modules are executable to perform operations including:

apply an interceptor to the selected line of code;

receive the live introspective data from the applied interceptor; and

display the received live introspective data received from the interceptor.

3 . The system of claim 1 , wherein the one or more modules are executable to perform operations including:

use the received live introspective data to create an entry call or an exit call.

4 . The system of claim 1 , wherein the one or more modules are executable to provide the user interface to display the stack trace including:

track a number of times a given a given one of the lines of code that are uninstrumented is called.

5 . The system of claim 4 , wherein the one or more modules are executable to prioritize the lines of code that are uninstrumented based on the tracked number of times each of the lines of code that is uninstrumented is called.

6 . The system of claim 1 , wherein the one or more modules are executable to provide the user interface to add or remove rules for detecting the lines of code that are uninstrumented.

7 . The system of claim 1 , wherein the one or more modules are executable to define a business transaction to include one or more of the lines of code that are uninstrumented.

8 . The system of claim 7 , wherein the one or more modules are executable to perform operations including:

identify performance issues with the defined business transaction.

9 . A method for detecting uninstrumented code in a monitored environment, the method including:

providing a user interface that displays an interactive dashboard of the monitored environment;

displaying, through the user interface, a stack trace that includes lines of code that are uninstrumented;

receiving a selection of one of the lines of code in the displayed stack trace;

displaying live introspective data on the selected line of code;

receiving input requesting the selected line of code to be instrumented and monitored; and

instrumenting the requested line of code and removing from display of the lines of code that are uninstrumented.

10 . The method of claim 9 , wherein displaying the live introspective data includes:

applying an interceptor to the selected line of code;

receiving the live introspective data from the applied interceptor; and

displaying the received live introspective data received from the interceptor.

11 . The method of claim 9 , including:

using the received live introspective data to create an entry call or an exit call.

12 . The method of claim 9 , wherein providing the user interface to display the stack trace includes:

tracking a number of times a given a given one of the lines of code that are uninstrumented is called.

13 . The method of claim 12 , including:

prioritizing the lines of code that are uninstrumented based on the tracked number of times each of the lines of code that is uninstrumented is called.

14 . The method of claim 9 , wherein providing the user interface includes proving an interface to add or remove rules for detecting the lines of code that are uninstrumented.

15 . The method of claim 9 , including defining a business transaction to include one or more of the lines of code that are uninstrumented.

16 . The method of claim 17 , including:

identifying performance issues with the defined business transaction.

17 . A non-transitory computer readable medium embodying instructions when executed by a processor to cause operations to be performed for detecting uninstrumented code in a monitored environment, the operations including:

providing a user interface that displays an interactive dashboard of the monitored environment;

displaying, through the user interface, a stack trace that includes lines of code that are uninstrumented;

receiving a selection of one of the lines of code in the displayed stack trace;

displaying live introspective data on the selected line of code;

receiving input requesting the selected line of code to be instrumented and monitored; and

instrumenting the requested line of code and removing from display of the lines of code that are uninstrumented.

18 . The non-transitory computer readable medium of claim 17 , wherein displaying the live introspective data includes:

applying an interceptor to the selected line of code;

receiving the live introspective data from the applied interceptor; and

displaying the received live introspective data received from the interceptor.

19 . The non-transitory computer readable medium of claim 17 , wherein the operations include:

using the received live introspective data to create an entry call or an exit call.

20 . The non-transitory computer readable medium of claim 17 , wherein providing the user interface to display the stack trace includes:

tracking a number of times a given a given one of the lines of code that are uninstrumented is called.

21 . The non-transitory computer readable medium of claim 20 , wherein the operations include:

prioritizing the lines of code that are uninstrumented based on the tracked number of times each of the lines of code that is uninstrumented is called.

22 . The non-transitory computer readable medium of claim 17 , wherein providing the user interface includes proving an interface to add or remove rules for detecting the lines of code that are uninstrumented.

23 . The method of claim 17 , wherein the operations include defining a business transaction to include one or more of the lines of code that are uninstrumented.

24 . The method of claim 17 , wherein the operations include:

identifying performance issues with the defined business transaction.