-
Want to start a conversation about what stands in the way of marking the `opentelemetry-semconv` artifact as stable. We've come a long way recently, re-organizing by domain, switching from build-tools…
-
### Description
A clear and concise description of what the bug is.
```
$ go mod tidy
go: finding module for package go.opentelemetry.io/otel/semconv/v1.21.0
go: finding module for package go.o…
-
## What
This package uses span names such as `GET /_next/static/webpack/4330e83422f91a86.webpack.hot-update.json`
OpenTelemetry explicitly specifies this [here](https://opentelemetry.io/docs/spe…
-
Describe in detail each Jinja2 filter, function, and test (both those defined in Minijinja and in Weaver).
We could also create an [mdBook](https://github.com/rust-lang/mdBook) that we will progres…
-
This issue will be used to track the work for making `hostmetricsreceiver` capable of transitioning to Semantic Conventions compliance.
Task list:
- [ ] Add feature to `mdatagen` to allow it to …
-
**Description**
Ed wrote in the spec release review voting thread with the following info.
> I have a question. This question pertains in both SemConv v1.27.0 and v1.26.0, so it is rel…
-
To properly support multiple registries with Weaver, we need to automatically generate the OTEL schema for a new version of a registry before packaging and publishing it. This issue focuses on definin…
-
### Component(s)
exporter/sentry
### What happened?
## Description
base on this picture `library_version` is invalid in Sentry error because is empty
![{57D8B281-558A-49C9-B87B-9065F17042EB…
-
Make `instrumentation/net/http/otelhttp` produce Client Metrics following the migration plan #5132.
A user should be able to produce Metrics from the `transport` in current semconv (default), and the…
-
## Preamble
I'm logging this as an issue to help other people facing it to find the explanation and solution but I believe the root cause is close to the one described in https://github.com/trinodb…