Currently the decorator @trace only support plain functions. Decorating functions with async makes the trace hierarchy incorrect.

        @runnable()
        async def test1(self):
            return '1'

        @runnable()
        async def test2(self):
            return self.test1()

        def test(self):
            asyncio.run(self.test2())

this generates

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

Allow people to safely export production traces into GitHub tickets (as a way of reproducing problems, especially with the UI) without exposing sensitive information.

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

The anonymizer is partially implemented.

Proposal - what do you suggest to s

From #276

Right now tempo-cli is a utility for debugging purposes but there are plans to extend its functionality.

Created this issue to track/discuss the improvements of the tool.

This coverage change came up in a PR #530 that did not touch the source code at all

It is likely that there is a race condition that makes this line not being executing in some cases. Need to make it more deterministic.

There are many packages required by product/test. We have some of them moved to a central place, but still many are left in individual projects. This issue is to track moving all the versions to a centralized place, so its easy to update when a need arises.
eg: open-telemetry/opentelemetry-dotnet#1506 (comment)

The current getting started guide assumes the user will be starting using the SDK building block packages like tracing, node, and metrics. In the future, it is expected most users will use the SDK package as a starting point and it would be better for the getting started guide to reflect that.

@thegryfon noticed that in community axios implementations, some leak contexts and you wouldn't necessarily know until a second root trace is attempted.

here's an example scenario I think tests could cover:

there is no parent trace in scope
create a client request
create a second client request
verify that both client requests are root spans

Cannot use same trace ID accross different node of microservices

On the document of https://opentracing.io/docs/overview/tracers/#propagating-a-trace-with-inject-extract, there is a concept of inject and extract. This is working fine with http carrier. Yet, I cannot reproduce this with Text Map carrier.

Please create a doc for u

See: elastic/apm-agent-nodejs#1482