On this page:

Your Rating:
Results:
PatheticBadOKGoodOutstanding!
15 rates

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

find-entry-points

Set this property to true to log all potential entry points that are hitting instrumented exit points or loggers to the Business Transactions log file.

Use this property when you suspect that some traffic is not being detected as business transactions. You should only enable this property for debugging purposes. You should disable this property in a production setup.

For new applications, you can use the interactive Live Preview tools to discover entry points.

Type:

Boolean

Default value:

false

Platform(s):

Java, .NET

heap-storage-monitor-devmode-disable-trigger-pct

The maximum Java heap utilization percentage for development mode.  If the heap utilization exceeds this value, development mode is automatically disabled.

Type:

Integer

Default value:

90

Range:

Minimum=0, Maximum=100

Platform(s):

Java

ibmbpm-systemtask-bt-naming

Decides BT naming scheme for IBM-BPM System Task POJO business transactions.

The property value is comma-separated identifiers chosen from projectbpdtask, and implementation, and is order-sensitive.

Type:

String

Default value:

default

Platform(s):

Java

Example

For example:

  value = project, task means that the POJO business transactions is named as: <project-name> / <task-name>
       value = task, project means that the POJO business transactions is named as: <task-name> / <project-name>
       value = none means that the POJO business transactions is not detected, in other words, disabled.
       value = default would mean that all the identifiers are used for BT naming are in default order, that is, they are named as:
                    <project-name> / <bpd-name> / <task-name> / <implementation-name>

jdbc-callable-statements

Use this property to indicate the implementation classes of the java.sql.CallableStatement interface that should be instrumented.

Type:

String

Default value:

none

Platform(s):

Java

Examples

For example, to instrument calls to Times Ten (an unsupported database), you could set this property to the following:

com.timesten.jdbc.JdbcOdbcCallableStatement

jdbc-connections

Use this property to indicate the implementation classes of the java.sql.Connection interface that should be instrumented.

Type:

String

Default value:

none

Platform(s):

Java

Examples

For example, to instrument calls to Times Ten (an unsupported database), you could set this property to the following:

com.timesten.jdbc.JdbcOdbcConnection

jdbc-dbcam-integration-enabled

Use this property to integrate the Java Agent with AppDynamics for Databases and Database Monitoring. Changes to this property do not require a JVM restart for JDK 1.6 and higher. Older 1.5 JVMs do not support class reloading, so for those environments, a restart is required.

Type:

Boolean

Default value:

false

Platform(s):

Java

More Info

AppDynamics for Databases: When this property is enabled, you can link to AppDynamics for Databases from a Transaction Snapshot Flow Map where an exit call is to an Oracle database, and analyze the SQL statements that were running at the time of the snapshot. This property works in conjunction with the AppDynamics for Databases license and database collector that has been previously set up. Integration must also be set up from the Admin pages of the Controller UI.  For more information, see Integrate and Use AppDynamics for Databases with AppDynamics Pro.

Database Monitoring: Set this property to enable snapshot correlation between Java applications and Oracle databases. This property configures Globally Unique Identifier (GUID) session tagging between business transactions monitored by the Java Agent and Oracle databases monitored by Database Monitoring. Each snapshot is identified by a GUID which Database Monitoring instrumentation injects into the Oracle session using a standard JDBC API. This enables AppDynamics to collect the session properties, including the GUID. When the queries are correlated with the GUID, AppDynamics can correlate the backend database activity with the business transaction snapshot.

jdbc-prepared-statements

Use this property to indicate the implementation classes of the java.sql.PreparedStatement interface that should be instrumented.

Type:

String

Default value:

none

Platform(s):

Java

Examples

For example, to instrument calls to Times Ten (an unsupported database), you could set this property to the following:

com.timesten.jdbc.JdbcOdbcPreparedStatement

jdbc-resultsets

Use this property to indicate the implementation classes of the java.sql.ResultSet interface that should be instrumented.

Type:

String

Default value:

none

Platform(s):

Java

Examples

For example, to instrument calls to Times Ten (an unsupported database), you could set this property to the following:

com.timesten.jdbc.JdbcStatement

jdbc-statements

Use this property to indicate the implementation classes of the java.sql.Statement interface that should be instrumented.

Type:

String

Default value:

none

Platform(s):

Java

Examples

For example, to instrument calls to Times Ten (an unsupported database), you could set this property to the following:

com.timesten.jdbc.JdbcOdbcStatement

jmx-appserver-mbean-finder-delay-in-seconds

When an app server starts up, the associated MBean server starts and the MBeans are discovered. The timing of these activities varies by app server and by configuration. If this activity is not completed in the time that the AppDynamics agent is expecting to discover the MBeans, then the MBean Browser will not show them. Using this node property, you can delay the discovery of MBeans to make sure that agent discovers all the domains after complete startup of the app server. For example, you can set the delay to a time which is 1.5 times of the server startup time. The default delay for the AppDynamics agent is two minutes.

Type:

Integer

Default value:

120

Platform(s):

Java

jmx-operation-timeout-in-milliseconds

Controls the length of time the Java Agent waits before timing out an MBean operation. If you have MBean operations that run longer than the default of 10 seconds, you can increase the timeout value up to 5 minutes.

Type:

Integer

Default value:

10000 (10 seconds)

Range:

1000ms (1 second) - 300000ms (5 minutes)

Platform(s):

Java

jmx-rediscover-mbean-servers

When an app server starts up, the associated MBean server starts and the MBeans are discovered. The timing of these activities varies by app server and by configuration. If this activity is not completed in the time that the AppDynamics agent is expecting to discover the MBeans, then the MBean Browser will not show them. Using this node property, you can trigger the rediscovery of MBeans to make sure that the agent discovers all the domains after complete startup of the app server. Set this property to true and reset the app agent, as described in Manage App Agents

Type:

Boolean

Default value:

false

Platform(s):

Java

jmx-query-timeout-limit

This property sets the timeout limit. Setting this property to negative will disable timeout. For example, if you set the property to –1, timeout is disabled.

Type:

Long

Default value:

5

Platform(s):

Java

 

 

jrmp-enable

 

jrmp-enable

This property enables or disables AppDynamics support for Sun RMI over Java Remote Protocol (JRMP). You should test Sun RMI JRMP support in a staging environment before using it on production systems. Enable Sun JRMP support by setting this property to true

Type:

Boolean

Default value:

false

Platform(s):

Java

leak-diagnostic-interval-in-minutes

The interval at which diagnostic data, content summary and activity trace, is captured for leaking collections.

Type:

Integer

Default value:

30

Range:

Minimum=2; Maximum=N/A

Platform(s):

Java

log-request-payload

Set this property to true to log the request payload—HTTP parameters, cookies, session keys, and so on— as part of a transaction snapshot. The log-request-payload property includes logging of WCF HTTP parameters for .NET.

Type:

Boolean

Default value:

false

Platform(s):

Java, .NET

logbased-visibility-log-check-interval-in-millis

How often the agent checks application log files for information related to garbage collection performance.

Type:

Integer

Default value:

1000 (ms)

Platform(s):

Java


  • No labels