Please answer these questions before submitting your issue.

• Why do you submit this issue?
• Feature or performance improvement

Question

• What do you want to know?
  I look into jedis-2.x plugin, find that enhanceClass is redis.clients.jedis.Jedis.
  But pipeline will directly invoke jedis client.
  Jedis --invoke---> client
  pipeline ---invoke-->client

There are two solutio

This issue tracks the changes required as part of switching over from gitter to slack:

• https://github.com/jaegertracing/jaeger/search?q=gitter - PR: #2868
• https://github.com/jaegertracing/documentation/search?q=gitter - Issue: jaegertracing/documentation#478
• https://github.com/jaegertracing/jaeger-ui/search?q=gitter
• https://github.com/jaegert

Describe the bug

make vendor-check fails when the path has spaces, for example /Users/username/Path With Spaces/work/savishy-tempo.
The error is docker: invalid reference format. which I have seen typically when Docker thinks we are passing it incorrect arguments.
I moved to a path without spaces i.e. /Users/username/savishy-tempo and make vendor-check works fine.
My first gue

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.

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.

As we are trying to make SigNoz deployment to work in common infra setups, a good first issue could be just trying installing SigNoz in their local setup and sharing if they face any issue.

Please share your infra details and did you face any issue in running SigNoz

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

@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