App Agent Node Properties (J-L)

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

Examples

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

com.timesten.jdbc.JdbcOdbcConnection

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.

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.

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

Examples

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

com.timesten.jdbc.JdbcOdbcPreparedStatement

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

Examples

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

com.timesten.jdbc.JdbcStatement

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

Examples

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

com.timesten.jdbc.JdbcOdbcStatement

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.

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.

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. 

This property helps to trigger the rediscovery of Mbeans periodically for every "x" mins (x being the value specified by this node property). When enabled, this property causes the agent to refresh its Mbean server cache for every specified amount of time. By default, no periodic rediscovery of Mbean servers is done. Set the value of this property to 0 to stop the periodic rediscovery task if enabled.

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.

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. 

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

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.

This property dumps all the HTTP data in the app agent logs. But data collectors "diagnostic data collectors" HTTP type are specific to show only the particular HTTP data and not everything, which is: cookies, header, session. The node property gives a complete HTTP dump.

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