App Agent Node Properties (D-E)

This property enables/disables the agent. When this property is set to true, TransactionEntryPoints will not be monitored. No new BTs or metrics will be registered, metrics, and snapshots will not be reported.  Agent background threads will not be stopped. When set to false, the agent becomes active immediately. It does not need a restart.

This property disables all calls to the agent-api library.  The calls function as no-ops when disabled.

Disables certain types of automatically detected exit points: SAP, Mail, LDAP, and so on. Type names are case sensitive. Use commas to separate multiple types.

Disable exit call correlation for a specific type of call. For example, KAFKA, WCF, WEB_SERVICE, HTTP, JMS, and RMI. By default, all exit call correlations are enabled.

Disables exit call monitoring for a specific type of exit call; for example, HTTP, JMS, WEB_SERVICE. If this property is set, the average data—calls/min, avg response time— for the specific exit call type is not collected. However, for a snapshot, all details are collected. Set this property if the application makes a large number of exit calls per transaction and the avg metrics are not important.

App agents that support percentile metrics enable collection by default. Disable percentile metrics on the Configuration > Slow Transaction Thresholds window or set this node property manually to true to disable percentiles. 

Changes to this property do not require an agent restart.

This property stops the BT-to-BT incoming cross-application metrics to be reported (but normal cross-application metrics continue to be reported, as expected).

This property controls correlation with web service transactions. When enabled, it prevents injection of the correlation header into a SOAP message if the WCF transport is not over HTTP or HTTPS.

For more information, see WCF Entry Points

Specifies types of data for which agent reporting to suppress. Use this property provides to disable data collection mechanisms at the agent to limit data reported by the agent for security or privacy reasons. This agent configuration overrides any Controller configuration that affects the data. 

You can disable 

• LOG_PAYLOAD: Log payload, such as the node property log-request-payload
• RAW_SQL: Raw SQL statements
• CUSTOM_EXIT_SNAP_DATA: Snapshot data in custom exits
• METHOD_INV_DATA_COLLECTOR: Diagnostic data collectors, method invocation
• HTTP_DATA_COLLECTOR: Diagnostic data collectors, HTTP requests
• INFO_POINT: Information points
• ALL: All of the above
• NONE: None of the above. This is equivalent to the default agent behavior. 

Examples

Configure disabled features in the app-agent-config.xml in the versioned conf directory for the agent. Specify the data category as the value attribute of the disabled-features property. You can have multiple data categories excluded by listing each separated by commas. For example:

With capture-raw-sql enabled, AppDynamics captures the SQL call in the following form: 

<app-agent-configuration>
  <configuration-properties>
        ....
        <property name="disabled-features" value="RAW_SQL,LOG_PAYLOAD"/>
  </configuration-properties>
  .....
</app-agent-configuration>

Sets whether data-collectors for IBM-BPM task business transactions should be disabled (value=true) or enabled (value=false).

Sets whether business transactions in-process correlation for IBM-BPM UserTask business transactions should be disabled (value=true) or enabled (value=false).

Sets whether business transactions naming scheme for IBM-BPM UserTask Business Transactions should be disabled (value=true) or enabled (value=false).
When it is set to true, the Business Transactions would be named as per the default URL and not the meaningful names.

The maximum number of transactions monitored per minute during development mode before the system switches out of development mode into normal operation mode.

Do not show these packages / class names in addition to the ones configured in the global call graph configuration, for the call graphs captured on this node. Does not need a restart.

If the agent cannot reach the controller for a prolonged period, it turns off most services and notifies the continuing tiers that upstream transaction was detected and is not being monitored. Set this property to true to enable the continuing tiers to detect their own transactions in the event of network failure on the upstream tiers.

This property enables the agent to recognize errors that occur in calls outside of or tangential to business transactions.

false: All business transaction errors are reported, but errors outside of the business transaction are not reported.

true: All business transaction errors are reported. In addition, errors outside of the business transaction are reported. For example, errors generated from tracking analytics for a business transaction are reported.

full-disable: No asynchronous errors are recognized.

By default the Java Agent automatically detects service endpoints for worker threads. Set this property to "false" to disable service endpoint detection for worker threads. This has the same effect as the Automatic Service Endpoint Detection checkbox for other types of service endpoints on Configuration > Instrumentation > Service Endpoints.

When EUM is enabled on applications implemented using the Servlet3 async dispatch mechanism, it is possible that multiple EUM correlation headers are added to the response.

This node property prevents duplicate ADRUM headers being injected in the HTTP response from Java Agent.

This node property is used to disable axon entry. By default, it is enabled.

This node property is used to disable axon exit. By default, it is enabled.

This property controls capture of per BT block and wait time metrics. It is disabled by default.

This property controls whether the agent captures the CPU time taken by a business transaction.

This property disables or enables automatic HTTP error code reporting for error codes between 400 to 505.

This property disables or enables the capture of information point calls in snapshots. When this property is set to true, information point calls appear in the User Data section of the snapshot.

This property enables or disables Instance tracking on this node. Does not need a JVM restart.

This property enables or disables security interceptors on this node. Set this property to true in environments where the Java 2 Security Manager is enabled.  If the Java 2 Security Manager is enabled, and this property is not set to true, then the agent will encounter SecurityExceptions, and will not be able to collect the data that it should.  Does not need a JVM restart.

Set this property to true to enable JSON bytecode instrumentation rules. AppDynamics instruments the get and getString methods within the package/class org.json.JSONObject when you set this value to true. Needs a JVM restart.

Set the enable-kafka-consumer to true to enable Apache Kafka consumer entry points. For more information see 'Apache Kafka Backends' on Java Backend Detection.

This property is related to Automatic Leak Detection (ALD) and enables or disables Object Size monitoring on this node. Changing this property does not need a JVM restart. ALD is supported for JVM version 1.6 and up.

This property controls correlation with web service transactions. When enabled, a node which receives a web service transaction may correlate that transaction with any downstream transactions. The ability to correlate depends on the particular web services framework. Currently, correlation is supported only by Apache Synapse and CXF frameworks. When disabled, the agent will not perform correlation through any web service tiers.

This property disables or enables the default detection of Spring Integration entry points. Set to false to disable.

Default detection of Spring Integration entry points is based on MessageHandler. In cases where a lot of application flow happens before the first MessageHandler is executed:

• Set this property to false
• Configure suitable POJO entry points
• Specify the property spring-integration-receive-marker-classes

See also Spring Integration Support.

This property enables to split web service business transactions on the SOAP XML payload. Set the value to true to enable the property. You can modify namespace context mapping (mapping of the prefix to URI) to parse SOAP message property in the app-agent-config.xml file.

This property disables or enables the policy for start-up transaction snapshot. This means snapshots are collected for all BTs for all invocations for the first 15 minutes of application server startup.

This property disables or enables transaction correlation. It does not require a restart.

Enable or disable servlet HTTP entry points and exit points for Vert.x.

Enable or disable Vert.x verticle message entry points for continuing transactions.

This property enables Java XML Binding and DOM Parser bytecode instrumentation rules. Set to true to enable. The change takes effect after a JVM restart.

Enables end-to-end message latency monitoring for distributed asynchronous systems by setting up a threshold. Any message taking more time than the threshold is viewable through the Event Viewer.

By default, configuring an exception to be ignored in the error detection settings prevents the ignored exception thus marking any Business Transaction that experiences it as in error. However, it does not prevent the occurrences of the exception being tracked in the Errors and Exceptions dashboard.  

To completely ignore certain exceptions, provide their fully qualified class names in this node property.

For example, oracle.jdbc.DatabaseException.

Multiple exceptions can be added that are comma-separated.

It is recommended to use this property with caution because it removes all visibility of the impact of exceptions configured in this way.