Handle Span drop message in APM Java agent

Kibana version: 7.4.0

Elasticsearch version: 7.4.0

APM Server version: 7.4.0

APM Agent language and version: Java and 1.9.0

Description of the problem including expected versus actual behavior. Please include screenshots (if relevant):

We are observing span drop is happening, while trying to collect the APM data with "trace_methods" enabled.
We tried to increase the "transaction_max_spans" to 50,000, but still it is there.

Could you please help here, to get all the span details without any drop.




you can try to increase the max_queue_size of the agent and/or the APM Server queue size.

Note that Elastic APM is not meant for or optimized for handling that many spans. What's your use case? Are you using the trace_methods option with wildcards?


Hi Felix,

Many thanks for your quick help here.

The trace_methods option is not mentioned complete wildcards in project level,but yes it is wild card inside a specific package.

Use case is to get all the details(spans) for a specific transaction call inside a Java class.



This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.