Automatic Discovery for Java

The Java Agent automatically discovers service endpoints. To configure service endpoint automatic detection settings, click to Configure on the Service Endpoints pane. You can configure the following settings:

  • For existing service endpoint detection rules, you can enable or disable the detection rule.
  • For servlet service endpoints, you can modify automatic naming as you would with servlet business transactions.
Note: The maximum limit for naming the service endpoints through automatic discovery is 99 characters.

POJO Service Endpoints

For the Java Agent to detect Plain Old Java Objects (POJO) service endpoints, you must do the following:

  • Create at least one POJO custom service endpoint definition and enable it. The agent only detects POJO service endpoints for enabled custom service endpoint definitions.

  • Verify automatic discovery for POJO service endpoints is enabled. It is enabled by default.

    Note: When you disable automatic discovery for POJO service endpoints, the agent doesn't detect custom service endpoints.

Asynchronous Worker Thread Service Endpoints

The Java Agent automatically detects asynchronous worker threads spawned within a transaction as service endpoints. The agent names worker thread service endpoints for the class name, for example, "worker1". There is no end-to-end latency metric for worker thread service endpoints.

To disable worker thread service endpoints, register the enable-async-service-endpoints app agent node property with a value of "false". See App Agent Node Properties.