Dropped spans when the transaction has more than 500 spans(default), how is it decided to drop which spans?

Elastic Observability APM
1

Kibana version : 6.8

Elasticsearch version : 6.8

APM Server version : 6.8

APM Agent language and version : JavaAgent 1.9

Original install method (e.g. download page, yum, deb, from source, etc.) and version : download tar.gz from elastic official site

Description of the problem including expected versus actual behavior. Please include screenshots (if relevant):
Spans are dropped when the transaction has more than 500 spans(default), how is it decided to drop which spans? Or the spans, after the limit 500 is reached, are dropped?
I just wanted to clarify on which merit the spans are dropped.
My concern is, what if they're the problematic ones, which need to be reviewed?

Response would be appreciated. Thanks!

2

After 500 spans have been recorded for a transaction, the agent will drop all further spans. See also https://www.elastic.co/guide/en/apm/agent/java/current/config-core.html#config-transaction-max-spans

3

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