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.
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.
Today our AspNetCore metrics instrumentation captures a small subset...
...of the attributes defined in the [spec semantic conventions](https://github.com/open-telemetry/opentelemetry-specification/bl
Discussed this in SIG meeting - the docs need to be updated to state support from node 8.12 and up.
Originally posted by @Rauno56 in open-telemetry/opentelemetry-js#2834 (comment)
As we're adding support for OpenTelemetry API bridges, it would be useful to know how much they're being used so we know whether to prioritize additional features in the bridge spec.
We can use otel.span_kind for this telemetry. All spans from the otel bridges should have otel.span_kind set. The APM Server is inferring this field for non-otel spans
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
Add a description, image, and links to the distributed-tracing topic page so that developers can more easily learn about it.
To associate your repository with the distributed-tracing topic, visit your repo's landing page and select "manage topics."
PagerDuty(https://www.pagerduty.com/) is widely used for on-call globally. We are welcome the contributions to support it as alarm notification channel.