App Agent Node Properties (N-R)

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.

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.

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.

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

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.

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.

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

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.

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:
  • rest-uri-segment-scheme
  • rest-num-segments
• {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).

Examples

See Using Default Settings and Using rest-transaction-naming Properties.

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.

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.