Incomplete transaction traces from Java APM

[dev_elk]

Kibana version: 7.2.0

Elasticsearch version: 7.2.0

APM Server version: 7.2.0

APM Agent language and version: Java

Browser version:

Original install method (e.g. download page, yum, deb, from source, etc.) and version: Download page

Fresh install or upgraded from other version?: Fresh install

Description of the problem: Java APM agent has been installed in the application servers with below specification -
OS: SUSE Linux Enterprise Server 12 SP1
Application server: Tomcat
Java version: java version "1.8.0_202"
Java(TM) SE Runtime Environment (build 8.1.051)
SAP Java Server VM (build 8.1.051 10.0.2+000
Transaction traces are not coming from the parent level. Only downstream SQL statements are visible, but none of the upstream connections are visible in the traces. No custom instrumentation/trace_methods/public API are being used currently.
Need help to understand why complete data is not captured by the APM.

[felixbarny (Felix Barnsteiner)]

Hi

See https://www.elastic.co/guide/en/apm/agent/java/current/supported-technologies-details.html#supported-networking-frameworks for what is currently supported out of the box.

Which connections are missing?

[dev_elk]

Hi,

We have installed in multiple application server types, all based on java.

UI servers - customer access this via browsers (Chrome, IE etc.)
API servers - customers access api urls via http clients. This can be either any integration connectors (boomi etc.) or via custom clients based on apache, ruby etc. We don't have a list as this is customer owned clients.
Job servers - customer access this via UI servers.

We are able to see only high level transactions and then sql queries related to them, but not able to view all transaction types.

We tried configuring "trace_methods", but didn't work. Could you please provide a sample configuration for "trace_methods".

[felixbarny (Felix Barnsteiner)]

@dev_elk

but not able to view all transaction types.

Could you elaborate on what you'd expect to see but is missing?

@dev_elk

Could you please provide a sample configuration for "trace_methods".

The documentation contains several examples: Core configuration options | APM Java Agent Reference [1.x] | Elastic. What was the value you tried? What is the root package of your Java application?

I'm still not exactly sure which connections are missing. Is it from UI servers to Job servers or API servers to Job servers?