You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just testing elastic apm with java agent, with a long running transaction I've noticed no spans are recorded after a certain amount of time.
I have inspected the logs (my app & apm-server) with no trace of possible causes.
After more digging and time spent debugging, I've found the following configuration transaction_max_spans, that was causing spans to be ignored after 500 count.
A message should be logged when transaction_max_spans has been reached for a transaction, ex: Transaction max spans 500 has been reached for id c82e1e0bb6d86f12. Further spans will be ignored. See config param transaction_max_spans.
The message should be logged with default configuration, so a level of INFO or WARN is appropriate.
The text was updated successfully, but these errors were encountered:
Just testing elastic apm with java agent, with a long running transaction I've noticed no spans are recorded after a certain amount of time.
I have inspected the logs (my app & apm-server) with no trace of possible causes.
After more digging and time spent debugging, I've found the following configuration transaction_max_spans, that was causing spans to be ignored after 500 count.
A message should be logged when
transaction_max_spans
has been reached for a transaction, ex:Transaction max spans 500 has been reached for id c82e1e0bb6d86f12. Further spans will be ignored. See config param transaction_max_spans.
The message should be logged with default configuration, so a level of INFO or WARN is appropriate.
The text was updated successfully, but these errors were encountered: