Search before asking

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

Description

The plugin HttpPlugin of nodejs agent not intercept the method http.get

Use case

No response

Related issues

No response

Are you willing to submit a PR?

• Yes I am willing to submit a PR!

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

Bug description

When the backend API responds with 500 error code then the loader on charts section loads infinitely

Expected behavior

Charts should show No Data like in trace table.

Version information

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/

Bug Report

If you use the B3 propagator with e.g. the Grpc.Core instrumentation then it fails to connect the parent spans to the new server spans because gRPC headers are always lower case.

The issue is that the B3 propagator does not store the headers as lower case and then this line in the Grpc.Core instrumentation does not do case-insensitive comparison: https://github.com/open-telemetry/

The opentelemetry-sdk-metrics-base currently contains an outdated example that is not linked by lerna and therefore uses (also outdated) packages from npm. This issue includes updating the example to the new metrics packages once they are released (0.28) to npm. The package should also be moved to the examples/ directory.

Intake API

Extend transaction Intake API to accept transaction.dropped_spans_stats.service_target_type and transaction.dropped_spans_stats.service_target_name.

Aggregated Metrics Calculation

Extend transaction.DroppedSpanStats to contain the service_target_* fields. For calculating related span m

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

@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