On this page:
Information points let you define custom metrics for your application based on code points you specify in your configuration.
Information points are very similar to data collectors. However, data collectors capture application data only in the context of a business transaction. An information point collects data from a given point in code across all business transactions. For information on data collectors, see Collecting Application Data.
Every information point comes with default metrics called code metrics. The code metrics are:
You can supplement the code metrics that you get by default by defining custom metrics (business metrics) for the information point. Business metrics reflect the value of runtime data, such as the method parameter, return value, or a value captured by getter chain on the object on which the identified method was invoked. The business metric value represents either the sum or average of the values of the code point you identify as the information point.
Information points can give you significant insight into how the performance of an application corresponds to business performance. For example, depending on the nature of your application, you could use it to resolve business questions such as:
A example of a practical use of an information point are ignored exceptions. Exceptions, especially one that occurs frequently, can contribute to CPU spikes in a JVM. If you configure the exception to be ignored in AppDynamics, for example, if it is generated in the underlying application framework and does not have a direct bearing on your application performance, it may not be readily evident to you when the exception is affecting your application. An information point that counts the exception occurrence can help you identify the additional overhead.
Before attempting to configure an information point, note that to apply the information point to .NET and JVM 1.5 applications you will need to restart the application server.
The easiest way to create an information point is from the call drill down view in the transaction snapshot for a business transaction that uses the method you want to instrument as an information point. When you find an invocation of the method in the call graph, right click on it and select the option for configuring instrumentation on this class/method.
Alternatively, create information points from More > Information Points page. You can also modify and remove existing information points .
Specify the class and method for which you want to collect information, along with other identifying information. For details on using the UI to configure code matching for an information point, see the equivalent information on configuring data collectors on Collecting Application Data. While data collectors differ from information points in the scope of the data collected, the configuration for each is very similar.
For information on configuring information points for PHP applications, see Configure Information Points for PHP.
To collect business metrics from the method, add a custom metric for the information point. The custom metric configuration settings let you specify the data to collect as the business metric.
You can view information point values in various places in the Controller UI, including the following:
enable-info-point-data-in-snapshotsnode property to true. When the
enable-info-point-data-in-snapshotsnode property is set, information point calls appear in the User Data section of the snapshot. For more information, see App Agent Node Properties.
For full-screen viewing, click What is an Information Point?