+

Search Tips   |   Advanced Search


Customize profiling settings for non-Java EE ARM instrumented applications for analysis

For analyzing other types of applications (for example, non-Java EE applications or C applications), first instrument the application for Application Response Measurement (ARM) data reporting. See Collect data from non-Java EE applications. When creating the profiling configuration for an ARM-instrumented application, you will typically select the ARM Performance Analysis analysis type on the Overview page under the Monitor page. This type by default collects all data reported by the ARM instrumentation in the application.

To customize the default settings:

  1. Select the ARM Performance Analysis analysis type, and click Edit Options to open the Edit Profiling Options wizard.

  2. On the Filters page, specify the application and transaction filters to indicate the type of data to gather. The filters that you specify will depend on what type of ARM instrumentation you implemented in the application. You can filter hosts, URLs, SQL calls, or any other data that the ARM APIs report. The filters indicate the type of data that you do want to collect (that is, they include, rather than exclude). Also see About filtering and sampling.

  3. On the Sampling page, you can limit the amount of data being collected by specifying a fixed percentage or a fixed rate of all the data to collect.

    • Sample a percentage of all transactions: The profiler will alternate between collecting and discarding calls.

      For example, with a setting of 25%, the first will be collected, the next 3 will be discarded.

    • Sample a specific number of transactions each minute: The first n calls (where n is the specified value) will be collected, and nothing else will be collected that minute. Thus, you will never receive more than n calls in any given minute.

  4. Click Finish.


Results

Now, when you start profiling, the specified data will be collected.

Also see About filtering and sampling.