distributed-tracing

Search before asking

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

Description

I am using InfluxDB as the storage, the InFluxDB is provided by cloud provider, it does't has admin privilege.
If SkyWalking try to create database, it will fail.
I think, SkyWalking should check if the database exi

To complete the issue #2749, there's one PR that needs some attention: #2850. At its current state, it adds the contents of the Jaeger UI build to a Go asset in an uncompressed format. This causes an increase of approximately 10MB to the binary size of the Query/all-in-one.

Ideally, we'd find a way to store the contents of the UI in a compressed format in the binary and serve the compressed ass

We support opentelemetry, so it should be possible to instrument ruby applications and visualise data on SigNoz. But we don't have lots of expertise in Ruby in the core team, so we have not tested this.

https://github.com/open-telemetry/opentelemetry-ruby

It would be good first issue for folks expert in Ruby to test this and report their findings. If this works fine, we can add this to our d

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/

Once this spec PR is merged, we might want to borrow the idea and do similar thing in this repo.

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

As specified in this APM agents spec, there might be different reasons for spans being dropped by APM agents.

In this case agents should collect statistics about the dropped spans in a transaction object as follows:

{
  ... ,

  "dropped_spans_stats": [
    {
      "type"

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