On this page:

Your Rating:
Results:
PatheticBadOKGoodOutstanding!
16 rates

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

show-packages

For the call graphs captured on this node, show the specified packages or class names in addition to the ones configured in the global call graph configuration. Does not need a restart.

Type:

String

Default value:

none

Platform(s):

Java, .NET

slow-request-deviation

The value in milliseconds for the deviation from the current average response time. This setting is used for evaluation of slow in-flight transactions. Also, see the slow-request-threshold property for more details.

Type:

Integer

Default value:

200

Range:

Minimum=10; Maximum=3600

Platform(s):

Java, .NET

slow-request-monitor-interval

In-flight requests are checked for slowness in the interval specified by this property. The value is specified in milliseconds.

Type:

Integer

Default value:

100

Range:

Minimum=0; Maximum=3600

Platform(s):

Java, .NET

slow-request-threshold

In-flight requests taking more time than this threshold (in ms) with a deviation greater than the slow-request-deviation property from the current average response time are monitored to capture hot spots.

Type:

Integer

Default value:

500

Range:

Minimum=0; Maximum=3600

Platform(s):

Java, .NET

spring-batch-enabled

Use this property to enable or disable OOTB BT Detection for Spring Batch.

 

 

Type:

Boolean

Default value:

True

Platform(s):

Java

 

spring-integration-receive-marker-classes

Use this property to specify the class and method you have identified as suitable POJO entry points for Spring Integration.

Based on the MessageHandler interface, the App Agent for Java by default automatically discovers exits for all channels except DirectChannel. In cases where a lot of application flow happens before the first MessageHandler is executed,

If the application code polls for messages in a loop, the span of each loop iteration is tracked as a transaction. Tracking begins when the loop begins and end it when the iteration ends. To safeguard against cases where pollableChannel.receive() is not called inside a loop, specify this property for each class/method combination that polls messages in a loop.

After setting this property, restart the application server for changes to this property to take effect.

Type:

Comma-separated string of fully-qualified class /method name, such as spring-integration-receive-marker-classes = <fully qualified name of class/method>,<> ....

Default value:

none

Platform(s):

Java

Examples

For example, to enable tracking for the following:

class MessageProcessor
{
void process()
{
   while(true)
   {
          Message message = pollableChannel.receive()
   }
}
}

set this property as follows:

spring-integration-receive-marker-classes = MessageProcesser/process

See also Spring Integration Support.

spring-mvc-naming-scheme

Register this node property to modify the naming scheme for Spring MVC transactions. Bean ID cannot be used as a global naming type. Use the bean ID and method name for global.

Type:

String

Allowed Values:

bean-id, simple-class-name, fully-qualified-class-name, business-interface-name, bean-method-name, ben-id-and-method-name, class-and-method-name

Default Value:

none

Platform(s):

Java

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: Enable Thread Correlation for Java.

Type:

Comma-separated string of fully-qualified class names or package names

Default Value:

none

Platform(s):

Java

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

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].

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

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" />

See serviceHostingEnvironment.

websocket-entry-calls-enabled

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

Type:

Boolean

Default Value:

true

Platform(s):

Java




  • No labels