Now some of the http client plugins record the username:password into the tag peer and url, this should be removed explicitly.

Example request url might be http://username:password@example.com

Split from jaegertracing/jaeger#2645 to track the work in other repos:

• jaeger-lib jaegertracing/jaeger-lib#85
• jaeged-idl jaegertracing/jaeger-idl#68
• jaeger-operator
• jaeger-client-java jaegertracing/jaeger-client-java#765
• jaeger-client-go https://githu

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

Tracking issue, similar to jaegertracing/jaeger#2645

Done:

• #548
• #549
• #550

Remaining:

• publish crossdock images
• remove .travis.yml
• update build badge in README
• change required checks to new GH jobs

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

It's confusing to have a NoopLogger in the API and in the SDK.

@obecny looks like we have a NoopLogger in the API and SDK. I'm going to close this, but open a new issue to remove the core NoopLogger

Originally posted by @dyladan in open-telemetry/opentelemetry-js#1523 (comment)

@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

Similar to jaegertracing/jaeger#2645

• migrate steps from .travis.yml to GHA workflows
• update build badges in README
• remove .travis.yml
• change required checks to new GH jobs

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