distributed-tracing

Search before asking

• I had searched in the issues and found no similar feature requirement.

Description

I find some configurations are in configurations.md , but not in the agent.config , such as agent.trace_segment_ref_limit_per_span 、agent.instance_properties[key]=value . Otherwise , the configuration ```

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

Is your feature request related to a problem?

The first step towards app optimization

Please describe.
Configure whyDidYouRender under the development env

**Note: make sure it is compatible with all the custom hooks that we are using in the project **

I think it would be to good to have a rpm/linux package for tempo backend like Grafana does (below), or at least official docs of how to install in a linux env without containers.

https://grafana.com/docs/grafana/latest/installation/rpm/

InMemoryExporter is designed for unit test purpose.

If OpenTelemetry .NET unit tests have some common need that cannot be achieved by InMemoryExporter, we would want to fix it in InMemoryExporter rather than inventing another exporter for tests.

The ask is to evaluate whether it is possible to get rid of https://github.com/open-telemetry/opentelemetry-dotnet/blob/0c93744d4ba51676b61ab1

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

https://open-telemetry.github.io/opentelemetry-js/

I clicked "SDK docs" in the readme, which took me to https://open-telemetry.github.io/opentelemetry-js/

There, I opened both the getting started guide and the node auto-setup thing in this paragraph:

To get started tracing your own application, see the Getting Started Guide. For more information about automatic instrumentation see @OPEN

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

please look at images

like this

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