Incorrect calling statistics about zorka HOT 1 CLOSED

In some circumstances it can. For example if GC pause occurs when method is executing. Tracer simply registers current time at the beginning of method, at the end of method and records difference.

Now there is another issue: sometime method execution time is bigger than sum of all registered methods called from it. There can be several causes of such behavior: some classes/methods can be excluded from tracing or automatically filtered out by tracer. Also in some circumstances tracer overflow can occur, ie. tracer will stop registering methods in order to not eat too much memory. See tracer.max.trace.records setting in zorka.properties.

from zorka.