distributed-tracing

Please answer these questions before submitting your issue.

• Why do you submit this issue?
• [ x ] Requirement

Question

• java agent support dubbo 3.0

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

Hello team, in PR jaegertracing/jaeger#2798 the tls connection is enabled in collector, it would be good to support configuring cipher for it.

It would be similar to the fluentd tls settings in https://docs.fluentd.org/configuration/transport-section#tls-setting, you can config the ciphers fi

Bug description

There is no fallback component when there is any unhandled Error in the React component

Please describe.
If this affects the front-end, screenshots would be of great help.

Expected behav

Is your feature request related to a problem? Please describe.
While configuring the Azure backend, one has to hardcode secrets into the Tempo YAML, which may cause a problem in some restrictive environments where automated scans of code repositories may reveal secret-like strings and cause InfoSec teams to panic.

Describe the solution you'd like
It would be great if we could avoid th

Similar to open-telemetry/opentelemetry-dotnet#2138, we can cut .NET Core 2.1 from support matrix, as .NET Core 2.1 is end of life next month (https://devblogs.microsoft.com/dotnet/net-core-2-1-will-reach-end-of-support-on-august-21-2021/).

Since most of the projects list NETSTANDARD2.0 as the supported one, and not .NETCore2.1, the changes may be minimal, and mostly r

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

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.

It seems to me that UTC is selected for on the wire representation of time as well as in the database (jaegertracing/jaeger#712), which sort of makes sense, at least with a somewhat naive handling of timezones. However, I think that the Jaeger UI should support displaying times in the timezone local to the user, i.e. of the browser as to reduce the mental load when viewing

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

@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

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