extend jar analyzer to all loaded libraries

[zeitlinger]

Is your feature request related to a problem? Please describe.

Jar analyzer currently reports only jars that have a .jar or .war extension.
It would be great to have an option to include internal jars as well - so that users can provide more context for troubleshooting - and for statistical purposes (e.g. what are popular libraries).

See

opentelemetry-java-instrumentation/instrumentation/runtime-telemetry/runtime-telemetry-java8/javaagent/src/main/java/io/opentelemetry/instrumentation/javaagent/runtimemetrics/java8/JarAnalyzer.java

Line 150 in 129f224

// Only code locations with .jar and .war extension should make it here

Describe the solution you'd like

see above

Describe alternatives you've considered

No response

Additional context

No response

[zeitlinger]

@jack-berg since you added this feature - wdyt?

[jack-berg]

It would be great to have an option to include internal jars as well - so that users can provide more context for troubleshooting - and for statistical purposes (e.g. what are popular libraries).

Could you elaborate on what you mean by internal jars? Which types of jars are currently being omitted?

[zeitlinger]

It would be great to have an option to include internal jars as well - so that users can provide more context for troubleshooting - and for statistical purposes (e.g. what are popular libraries).

Could you elaborate on what you mean by internal jars? Which types of jars are currently being omitted?

I would like to see that my spring boot app is using spring framework, spring data, etc.
Maybe it should be "library" rather than "jar".