Jay DeLuca

does anyone think this issue is still needed at this point? I haven't had any problems but I'm also on a pretty powerful machine

I wrote a script to identify all the library instrumentations and then whether or not they have a readme: - [ ] [alibaba-druid-1.0](https://github.com/open-telemetry/opentelemetry-java-instrumentation/tree/main/instrumentation/alibaba-druid-1.0/library) - [x] [apache-dbcp-2.0](https://github.com/open-telemetry/opentelemetry-java-instrumentation/tree/main/instrumentation/apache-dbcp-2.0/library) - [ ] [apache-httpclient-4.3](https://github.com/open-telemetry/opentelemetry-java-instrumentation/tree/main/instrumentation/apache-httpclient/apache-httpclient-4.3/library)...

was there a mechanism/script used to generate the list of instrumentations that need this? I noticed a few that I looked at might already be done ([jaxrs](https://github.com/open-telemetry/opentelemetry-java-instrumentation/blob/main/instrumentation/jaxrs/jaxrs-1.0/javaagent/src/main/java/io/opentelemetry/javaagent/instrumentation/jaxrs/v1_0/JaxrsCodeAttributesGetter.java) for example). I...

I'm not sure how consistent this needs to be across languages, but just for context, we are doing things a little differently in java for our instrumentation configs, [example](https://github.com/open-telemetry/opentelemetry-java-instrumentation/blob/f31f574d9d02cf80ad1198b766f89e5acc2981f0/smoke-tests/src/test/resources/declarative-config.yaml#L23-L28). for...

Hey @KazzmanK, as @pheyken points out, it doesn't look like you are using prometheus for your caffeine metrics, so you might want to open an issue with [micrometer](https://github.com/micrometer-metrics/micrometer) instead.

Capturing input from @jackshirazi around scope information: > Having all of the fields from the InstrumentationScopeInfo object available to be able to re-construct it is useful because it is used...

Update on the current state of things: - Automated target version discovery for both javaagent and library instrumentation types - Instrumentation classification via metadata.yaml - Whether instrumentation is disabled by...

adding a note that @laurit brought up [here](https://github.com/open-telemetry/opentelemetry-java-instrumentation/pull/13825#discussion_r2081117147) about certain modules containing multiple instrumentations: > An alternative to this would be to allow metadata.yaml to describe multiple instrumentations. I guess...

Capturing some notes from the discussion at todays SIG meeting: - We should target eventually publishing this information (or parts of it) to the registry in opentelemetry.io, this will allow...

Making note that @zeitlinger [had a question](https://github.com/open-telemetry/opentelemetry-java-instrumentation/pull/13965#pullrequestreview-2887850424) about the spring starter [configuration metadata file](https://github.com/open-telemetry/opentelemetry-java-instrumentation/blob/main/instrumentation/spring/spring-boot-autoconfigure/src/main/resources/META-INF/additional-spring-configuration-metadata.json): > do you have an idea if we can also generate the spring metadata out of...