Kong/kong-plugin-zipkin

Latency missing

subnetmarco opened this issue · 3 comments

When using the zipkin plugin, I am seeing traces like:

screen shot 2018-08-17 at 3 17 03 pm

I am not seeing any latency value for the access, balancer, etc spans - is this intended?

That is expected if the access/balancer phases took a negligible (i.e. 0) amount of time (which is common depending on choice of plugins).
Also keep in mind that kong only rarely updates the time via ngx.update_time. This was improved in Kong/kong@a08ff0c

@james-callahan wouldn't the latency still be there, with value 0 ? It seems like it's actually missing completely.

If you enlarge the span it should be there (as 0).