Interoperate with shaded classes

[robododge]

Hi,

Problem statement

My target application has many shaded opensource libs.

Detail

I ran across a bit of a road block with auto instrumentation of my company's runtime library because the code I am trying to instrument is an "agent-like" jar called DME which has shaded quite a few opensource libraries.

Example:
They have shaded the standard jetty packaging:

• ORIGINAL : org.eclipse.jetty.client.HttpClient
• SHADED : com.acme.dme.jetty.client.HttpClient

This is old code, luckily it had been upgraded to run in a 1.8 runtime, but making any changes to it is not an option. A lot of these shaded libraries are ones that Otel auto instrumentation looks for and uses.

A few others that are shaded:

• org.apache -> com.acme.dme.apache
• org.mortbay.util -> com.acme.dme.mortbay.util
• com.google.common -> com.acme.dme.google.common

Ideas

The only approach I can think of is to create my own orphan build and apply the exact shading rules to the opentelemetry-javaagent classes so that the names of these classes bundled in opentelemetry-javaagent-all.jar now match exactly with the com.acme.dme package structure. Most all of the agent classes will still be in inst. but I need to move quite a few of them and to com.acme.dme.

Is there any recommendations or ideas for handling target applications with shaded libraries?

[robododge]

I may be overthinking, the instrumentation module should have what I need,maybe through the helper class mechanics or the class loader matching to find the right classes to apply Advice. After a class match is made, the instrumentation's Advice will take over with no need to alter the class names internally .