Search before asking

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

Apache SkyWalking Component

OAP server (apache/skywalking)

What happened

1. Set SW_PLUGIN_HTTP_INCLUDE_HTTP_HEADERS=x-request-id,x-correlation-id in environment.
2. OAP-Server Set `SW_SEARCHABLE_TAG_KEYS=http.method,http.he

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

Actual the windows executables (jaeger-agent.exe, jaeger-collector.exe, ...) don't have a version set. It is hard to identify the current used version and check if the actual used version is outdated.

Probl

@ankitnayan https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md#running-puppeteer-in-docker

Originally posted by @pal-sig in SigNoz/signoz#508 (comment)

Describe the bug

The query-frontend logs some details about the query when it completes, for example:

level=info ts=2021-11-25T11:32:38.59660534Z caller=handler.go:96 tenant=1 method=GET traceID=57060d6b589d1903 url="/tempo/api/search?x-dbg-exhaustive=true&limit=20" duration=7.079269575s response_size=96 status=200

If you cancel the request before it completes, this log does

Bug Report

The current OTLP exporter below flattens nested array in Span.Atttributes (Activity.Tags in .NET) into a list of key value pairs with the same key for all these kv pairs. For example, activity.SetTag('arraykey', new int [] {1, 2, 3} is converted to JSON like list {{'arraykey': 1}, {'arraykey': 2}, {'arraykey': 3}} in OTLP. This could cause problem if the OTLP listener would lik

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

Upgrading to @opentelemetry/sdk-metrics-base@0.26.0 and @opentelemetry/exporter-prometheus@0.26.0, all metric names are postfixed with _total. This has impacted all our grafana dashboards. Is this anywhere documented, I couldn't find. And any reason why such post fix is needed?

Example:
Old metric name: incoming_event
New metrics name (just by upgrade): incoming_event_total

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