Trask Stalnaker
Trask Stalnaker
I believe the problem is that somehow the `.github` directory name in that repo ends with a space (see the encoded `%20` in the link below): https://github.com/open-telemetry/sig-end-user/tree/main/.github%20/ISSUE_TEMPLATE
hi @ataraxis! we had a similar report that was fixed in 2.12.0 it looks like you're already using that version, so could you take a look at https://github.com/open-telemetry/opentelemetry-java-instrumentation/pull/13047 and see...
I agree it reads a bit confusing, I think a clarification PR would be welcome
> was there a mechanism/script used to generate the list of instrumentations that need this? I may have used something like this: ``` grep -r --include=*.java controllerTelemetryEnabled . | grep...
Closing, we've added to all the controller spans where it's readily available, and we can revisit others on demand
(in particular) > Stable instrumentations authored by OpenTelemetry SHOULD NOT produce telemetry that is not described by OpenTelemetry semantic conventions.
I suspect this issue relates to `--base` modeling [Base URL](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/base), while probably what you want in this case is the upcoming [--root-dir](https://github.com/lycheeverse/lychee/pull/1576)
hi @Kielek! in Java, the instrumentation libraries use a "compileOnly" dependency on the instrumented libraries, which avoids this: > if the end-user references OpenTelemetry.Instrumentation.Hangfire it automatically brings packages licensed by...
Blocked on #2558