Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Log when tranasction_max_spans reached #849

Closed
cdalexndr opened this issue Sep 18, 2019 · 0 comments · Fixed by #890
Closed

Log when tranasction_max_spans reached #849

cdalexndr opened this issue Sep 18, 2019 · 0 comments · Fixed by #890
Labels
good first issue Good for newcomers
Milestone

Comments

@cdalexndr
Copy link

cdalexndr commented Sep 18, 2019

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants