Requirement - what kind of business use case are you trying to solve?

Always use time units in the Web UI which are easy to read by humans.

We use Jaeger to trace some complex, long-running offline jobs in which a seconds granularity in the Web UI is too fine-grained for human consumption.

Problem - what in Jaeger blocks you from solving the requirement?

Currently, durations seem

I understand that we use 'cls' for context storage/thread local storage. However, it is a little painful for me right now to try to get spans from thread local storage, that is because there are many moving parts: I need to initialize the tracer or get the global tracer (will creating a new tracer work?) and then check the current context but then check if the contextManager has a rootSpan. Also g

Thanks for the good examples.
There's warning when running example/queue:
queue/runner.py:19: DeprecationWarning: Application.make_handler(...) is deprecated, use AppRunner API instead

python 3.7.2
aiozipkin==0.5.0
aiohttp==3.5.4
aiojobs==0.2.2

Checked latest aiohttp doc., maybe need to update like this (it works without warnings):

# /examples/queue/runner.py
def ru

All jaeger components are licensed under APL v2: https://github.com/jaegertracing/jaeger/blob/master/LICENSE

Need to get agreement from all contributors before changing license: @jukylin @ldjdd @Liv1020 @aogier @corerman @sadok-f

The metric pace_postgres_query_duration_seconds is described as seconds:
https://github.com/pace/bricks/blob/fa06ccdc029fb3f0ec91796d8064d84c92d187de/backend/postgres/postgres.go#L89-L91

But the actual values gathered are milliseconds:
https://github.com/pace/bricks/blob/fa06ccdc029fb3f0ec91796d8064d84c92d187de/backend/postgres/postgres.go#L246

I think we should gather the seconds and ma

This will remove the main crate's dependency on Prometheus.

See the cargo workspace docs for more info on how we can accomplish this.

https://github.com/jaegertracing/jaeger-client-java/blob/master/jaeger-core/src/main/java/io/jaegertracing/samplers/GuaranteedThroughputSampler.java

Use an audit tool such as Polaris and eliminate as many warnings as possible by default for jaeger chart.

There's already a constant for it: TRACER_IP_TAG_KEY.

Jaeger uses ip tag to group spans around individual machines for clock skew adjustment and with futures it's easy to mess up and make child spans outlive parents, triggering time travel bamboozle:

• https://gith