On this page:

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

socket-enabled

Use this property to enable NetViz monitoring of .NET apps running on Windows.

Type:Boolean
Default value:false
Platform(s):.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 = ,<> ....
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()
   }
}
}
CODE

set this property as follows:

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

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