AppDynamics switched from Semantic Versioning to Calendar Versioning starting in February 2020 for some agents and March 2020 for the entire product suite.


    Skip to end of metadata
    Go to start of metadata

    This reference page contains information about app agent node properties. The properties are listed in alphabetical order.

    In general use caution when modifying the agent default settings. If increasing limits specified for an agent, you need to carefully assess and monitor memory consumption by the agent after the change.

    normalize-prepared-statements

    When this flag is set to true, any variables in prepared statement SQL would be substituted with '?' before query text is added to any snapshots.

    Type:Boolean
    Default value:true
    Platform(s):Java

    nservicebus-single-threaded

    Specify the threading architecture for the NServiceBus message queue. The value defaults to true. For multithreaded queue implementations, change the value to false. See NServiceBus Backends for .NET.

    Type:Boolean
    Default value:true
    Platform(s):.NET

    osb-ignore-exit-types

    This comma-separated property defines which exits protocols (as configured in the Transport Configuration pane) are excluded from detection as uncorrelated custom backends.

    Set the property to 'all', if you do not want to detect any exit.

    Type:String
    Default value:http,jms
    Platform(s):Java

    on-demand-snapshots

    Collect snapshots for all Business Transactions executed in this node. Does not need a restart. This property is ignored in the Development mode. 

    Type:Boolean
    Default value:false
    Platform(s):Java, .NET

    percentile-method-option

    You can choose one of two different algorithms to calculate percentiles in AppDynamics:

    • P Square algorithm (default): This option consumes the least amount of storage and incurs the least amount of CPU overhead. The accuracy of the percentile calculated varies depending on the nature of the distribution of the response times. You should use this option unless you doubt the accuracy of the percentiles presented.
    • Quantile Digest algorithm: This option consumes slightly more storage and CPU overhead but may offer better percentiles depending on how the response times are distributed.

    Changes to this property do not require that you restart the agent.

    Type:Numeric
    Supported Values:
    • 1: P Square
    • 2: Quantile Digest
    Default value:1
    Platform(s):Java, .NET

    queue-single-threaded

    Specify the threading architecture for the IBM MQ message queue. The value defaults to false.

    When the IBM MQ Get() method is called, the transaction/snapshot is ended prematurely. To prevent this, set the agent node property: queue-single-threaded=true.

    Type:Boolean
    Default value:false
    Platform(s):Java, .NET

    reportingFrequencyInMillis

    The agent property specifies the frequency of Request Segment Data (RSD) uploads from the agent.

    Type:Numeric
    Default value:10000 ms
    Platform(s):Java



    rest-num-segments

    The property, rest-num-segments specifies the n in the first-n-segments parameter in rest-uri-segment-scheme. If this property is 0 or less, then the value of this property is ignored. The value of this property is also ignored if rest-uri-segment-scheme=full.

    Type:String
    Default value:2
    Platform(s):Java

    rest-transaction-naming

    This node property determines the format in which REST-based business transactions are named. You can use variables to populate the name with values bound at runtime. Any characters in the property value that do not match a variable are treated as literal text in the business transaction name, so you can, for example, separate variables with a colon, slash, or another character.

    The agent takes each parameter and fills in the proper value based on the annotations and properties of the Java class: 

    • {class-name}: The app agent will fill in the name of the Java class mapped to the REST resource.
    • {method-name}: The method being called.
    • {class-annotation}: Class annotation values.
    • {method-annotation}: Method annotation applied to the method (not always present).
    • {rest-uri}: URI of the REST resource. The REST URI is further configured using the following properties:
    • {http-method}: HTTP method of the request, GET, POST, and so on.
    • {param-%d}: A parameter to the method identified by position. Replace %d with the position of the parameter (ZERO-based).
    Type:String
    Default value:{class-annotation}/{method-annotation}.{http-method}
    Platform(s):Java

    rest-uri-segment-scheme

    The property, rest-uri-segment-scheme has three valid values: first-n-segments, last-n-segments, and full. This property indicates how many segments of the URI to use for the URI in {rest-uri}. This option is case-sensitive. If the value of this property is full, then the value of rest-num-segments is ignored.

    Type:String
    Default value:first-n-segments
    Platform(s):Java


    rmqsegments

    The App Agent for .NET (agent) automatically discovers RabbitMQ remote services. Use the rmqsegments node property to refine the queue backend name to include some or all segments of the routing key. You must be familiar with your implementation RabbitMQ exchanges and routing keys. See RabbitMQ Exchanges and Exchange Types.

    The RabbitMQ routing key is a string. The agent treats dot-separated (".") substrings of the routing key as segments. Set the value for rmqsegments to an integer that represents the number of routing key segments to include in the name. For more details, see information on refining backend naming in RabbitMQ Backends for .NET.

    Type:Numeric
    Value:Integer representing the number of routing key segments to include in the name.
    Default value:0
    Platform(s):.NET

    • No labels