Please answer these questions before submitting your issue.

• Why do you submit this issue?
• Feature improvement

skywalking 8.3 add springmvc plugin reactive api support , but that cant collect HTTP statusCode, hope somebody can improve it

https://github.com/jaegertracing/jaeger/pull/2657/checks?check_run_id=1486634709#step:5:346

=== RUN   TestBuilderWithCollectors/with_collector_connection_status_ready
    builder_test.go:182: 
        	Error Trace:	builder_test.go:182
        	Error:      	Not equal: 
        	            	expected: int(1)
        	            	actual  : int64(0)
        	Test:       	TestBuilderWith

Is your feature request related to a problem? Please describe.
Need the ability to search all blocks directly for an id

Describe the solution you'd like
The tempo-cli should be extended to search all blocks for a specified tenant for a given trace id. It should show all found instances of the id and include information about the found traces to determine if they are equal. Perhaps j

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.

After the merge of this PR: open-telemetry/opentelemetry-dotnet#1548

We should create more unit tests just like open-telemetry/opentelemetry-dotnet#1537 to validate the full behavior.

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

Our traces contain data that is covered by GDPR (european user privacy regulations) and, thus developers do not have direct access to all traces. If an error occurs, relevant traces has to be filtered out and the relevant ones are forwarded to the developer.

Another use case:
It would be nice to just attach files with

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

Is your feature request related to a problem? Please describe.

The .. module has a conditional dependency on the parseurl library. This library is not an agent dependency. However, if parseurl is present then the agent will use it instead of it's own home grown URL parsing.

We've had users report that this conditional `re