Instrumentation Finder

This section is divided into two sub-sections:

  • Auto Instrument
  • Auto Discover

Auto Discover

Auto Discover feature is used to discover loaded packages, classes, methods and modules of the selected application instance.

To use this feature, click the Instrumentation Finder icon  on the left panel, a window is displayed where user can discover the settings based on the provided inputs. Click the Auto Discover tab.

Below is the description of each field displayed in this window:

  • Agent Type: Type of agent for instrumentation.
  • Connected Agent(s): List of all connected agents with the combination of Tier, Server, and instance key to show in drop down list.
  • Discover by filter: Auto discovery only for the specified classes and methods.
  • Discover All: Auto discovery for all packages, classes and methods.

In addition to that, ND Config UI provides interface to create and update the instrumentation profiles.

To do this, select the Autodiscovered instance from the drop-down list and click the Open button. Below is the screen prototype for showing all the packages, classes and methods in a tree structure.

  • In the left panel, there is a drop-down listed all the loaded agents data, by clicking on any one of them lists down all the data regarding their agents into the tree structure.
  • In Java case, all the packages, classes and methods are displayed into the hierarchical structure by selecting a particular node and clicking on “Instrument ” button.
  • After selecting all the instrumented methods from the right panel, user needs to provide the instrumentation profile name and click “Save” button to save the instrumentation profile.
  • Clicking the Save button converts all the selected nodes into an XML file which user can use for instrumentation purpose.

Applying Method Monitor for a Profile

This feature is used for creating the Method Monitors from Auto Discover or Auto Instrumentation screen.

Earlier, to add a method monitor to a profile, user was needed to navigate to Method Monitor screen and manually add the method monitors by providing FQM, which is a time-consuming task and involved high probabilities of wrong entries from the user side.

The new approach is more reliable as user is just required to select the package, class, and method and the profile where to apply this method monitor.

Upon selecting a method and clicking the Method Monitor button, user is prompted to select the profile to which method monitor is to be applied.

Once the profile is selected and Save button is clicked, the selected method monitor is added to the specified profile.