What causes gaps in span

Elastic Observability APM
1

Kibana version: 6.7.1

Elasticsearch version: 6.7.1

APM Agent language and version: Java

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

tempsnip
tempsnip1645×551 20.1 KB

Using the APM I see that there are gaps in the span timelines. I'm wondering, is the cause of this because I haven't got a trace method setup for the class that the transaction is calling through to? Or is it an issue with my sample rate (not set to 100). Just seeing if there's any info here on the most likely issue so that I can look into it.

P.S. It's also very possible that this timeline graph doesn't do what I expect it to do.

2

It's as you assumed- most of the transaction handling time is spent on non-traced code. See here a list of options of manually getting your code traced.
In addition, we are already working on automatically inferring spans, which may be fill such gaps nicely. It is still WIP, but I suggest you follow this PR and check it out.

1 Like
3

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