Some spans are missing in a transaction and span parent child relationship (Child span starting position) is incorrect in APM Timeline.
See original GitHub issueDescribe the bug
Some spans are missing in a transaction and span parent child relationship (Child span starting position) is incorrect in APM Timeline for the sample app attached.
Steps to reproduce
Agent Used : elastic-apm-agent-1.14.1-SNAPSHOT.jar Configuration used : Attached. Use the attached sample war give the input Lower : 1000, Upper : 1200 and compare the results in APM and sample war output. Attached sample screenshots for comparision.
Expected behavior
All spans should appear in APM and span parent child relationship should be correct.
Debug logs
Attached
Click to expand
replace this line with your debug logs
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Span records missing transaction.name
The issue here is that Span events are sent continuously from the agent as they end, but the trace itself is doesn't get...
Read more >Spans | APM Overview [7.15] - Elastic
Spans contain information about the execution of a specific code path. They measure from the start to the end of an activity, and...
Read more >Elastic APM RUM Missing nested spans - Stack Overflow
Some spans are translated into transactions, and nested spans may not be recorded. If I declare a page wide transaction, Angular's ngOnInit can ......
Read more >Distributed Tracing in Practice - Lightstep
Distributed Tracing: A History of Pragmatism. 202. Request-Based Systems ... Span with a defined parent-child relationship.
Read more >All other San Diego fixes - ServiceNow Docs
Indexed source filters are applied incorrectly between child tables ... in the 'Application services' UI under parent relationships.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@felixbarny checked with new configuration options and it seems working will keep testing for high response times and let you know if any issues.
Ah, yes, this is probably because the name of the configuration options have changed: https://www.elastic.co/guide/en/apm/agent/java/master/_unreleased.html#_potentially_breaking_changes