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

thread-correlation-classes

For multi-threaded applications, use this property to configure classes to be included in Java thread correlation when simple prefix-matching (matching on STARTSWITH) is sufficient to identify the classes.

The thread-correlation-classes property specifies the classes to include for thread correlation. This property can be used together with the thread-correlation-classes-exclude property.

The configured correlation takes effect without requiring a restart of the managed application.
Also see, Configure the Thread Correlation in Java Agent.

Type:Comma-separated string of fully-qualified class names or package names
Default value:none
Platform(s):Java

This property is not recommended for use in the Executor Mode.


thread-correlation-classes-exclude

For multithreaded applications, use this property to configure classes to be excluded in Java thread correlation when simple prefix-matching (matching on STARTSWITH) is sufficient to identify the classes. This property specifies the classes to exclude from thread correlation. This property can be used in conjunction with the thread-correlation-classes node property.

The configured correlation takes effect without requiring a restart of the managed application.
See Configure Multithreaded Transactions (Java only)

Type:Comma-separated string of fully-qualified class names or package names
Default value:none
Platform(s):Java

This property is not recommended for use in the Executor Mode.

thread-cpu-capture-overhead-threshold-in-ms

Determines the timeout allotted for collecting and calculating Thread CPU Time for 1000 iterations. If the timeout is exceeded, the Java Agent automatically disables CPU time collection for threads. CPU usage information will then be absent from the BT overview or snapshots in the Controller UI. In addition, an INFO-level log similar to the following appears in the logs:

[Thread-0] 22 Oct 2013 14:19:26,346 INFO JVMThreadCPUTimeCalculator - Disabling BT CPU Monitoring. Time taken to calculate Thread CPU Time for [1000] iterations is [15 ms] which is greater than the allowed budget of [10 ms].
CODE

This issue may particularly affect JDK 1.6 on Linux due to the issue getCurrentThreadCpuTime is drastically slower than Windows Linux.

Type:Integer
Default value:10 ms
Platform(s):Java

Examples

You can increase the thread-cpu-capture-overhead-threshold-in-ms property, but it is important to note that this may result in increased overhead on your application. We recommend you use this Java HotSpot VM option instead to speed up the API call itself:

-XX:+UseLinuxPosixThreadCPUClocks
CODE

Restart is needed after changing this value.

wcf-enable-eum

Enable and disable EUM correlation from a WCF node.

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

Examples

The enable EUM correlation, the WCF application must also have the following entry in the Web.Config:

 <serviceHostingEnvironment aspNetCompatibilityEnabled="true" />
CODE

See serviceHostingEnvironment.

websocket-entry-calls-enabled

When set to false, no WebSocket entry calls are detected.

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