Lauri Tulmin

@garydgregory with the latest semconv artifact it is `io.opentelemetry.semconv.ServiceAttributes.SERVICE_NAME`

@garydgregory what is the issue that you have?

If you are interested in working only one a subset of instrumentations you could try commenting out most of the instrumentations in `settings.gradle.kts`. It is a bit of a hit...

> do you have a hint? Do not use lambdas, or move your code to a later point where using lambdas does not crash the old jdk8.

@zeitlinger Have a look at how the test is implemented https://github.com/open-telemetry/opentelemetry-java-instrumentation/blob/main/smoke-tests/images/servlet/servlet-3.0/src/main/java/io/opentelemetry/smoketest/matrix/GreetingServlet.java Inside the test servlet it makes another request to second servlet. You should only see the header on the...

My guess is that if you examine the dependency tree you'll see that `opentelemetry-api` version is older than `1.40.0` that should be set by `opentelemetry-instrumentation-bom:2.6.0`. If you are importing multiple...

Could you provide a minimal application that reproduces the issue.

I'm not sure this is worth the effort, perhaps it would be sufficient to just document that trace and span id won't be available when otel appender is used along...

One way to resolve most of the (not all) typing issues would be to change `DefaultHttpClientInstrumenterBuilder` to `DefaultHttpClientInstrumenterBuilder` Then I think only `addClientAttributeExtractor(AttributesExtractor

> agree - but then we're making breaking api changes that is fine, we can deprecate the existing method and remove it in the next release.