Configuration Notes

  • The Apply to new Business Transactions option applies the collector to business transactions created after you have configured the data collector. Otherwise, the data collector applies only to the business transactions you select in the subsequent data collector configuration pane.
  • For Class, select the match condition that the data collector can use to identify the class, such as class name, implemented interface name, and so on. If matching by class name, then use the fully qualified name of the class, as appropriate for the application platform. For example, the form of the equals field value would be:
    • In Java: com.appdynamics.model.Item
    • In .NET: Bookstore.Item
    • In PHP: book

  • Is this Method Overloaded: this is an overloaded method, then add parameters that identify the signature. You must create a data collector definition for each form of the method for which you want to capture data. For example, given the overloaded method in this table, to capture data for only the second two forms, you would need to create two data collectors. The parameters to configure are shown:

    Signature Parameters to Configure
    getName()
    • None
    getName(int studentId)
    • Param Index 0: java.lang.int
    getName(int studentId, string name)
    • Param Index 0: java.lang.int
    • Param Index 1: java.lang.String

  • You can refine the method selection to meet specific conditions. If you configure more than one match condition, then all match conditions must be satisfied by the request for the data collector to be applied to the request.

  • Once you identify the method, specify the code point from which you want to capture data, such as the method return value, argument, or a value captured by the getter chain on the invoked object. Configure this code point in the Specify the Data to Collect from this Method Invocation section of the configuration settings.

  • HTTP data collector can capture data from HTTP parameters, request attributes, cookies, and other data. The names of these properties need to match exactly: no wildcards are supported. Notice that the Content-Length HTTP header is already captured in Splunk AppDynamics as the Average Request Size metric. However, you may choose to configure a data collector for this header to have the value appear in transaction snapshots, providing you insight into, for example, whether message size corresponds to slow performance.

  • You can configure multiple data collectors. The effect of multiple data collectors is cumulative. For example, if you add a custom data collector that does not include the collection of the URL HTTP request attribute, but keep the Default HTTP Request Data Collector configuration in which the URL is configured to be collected, then the URL is collected.