Description
Is your feature request related to a problem? Please describe.
Describe what the problem you have encountered; e.g I'm always frustrated when [...]
We are using Custom Instrumentation Hook feature to create spans around methods from COTS system for which no traditional instrumentation is available. Everything works out really well except all the spans are named with Package.Method by default which does not help in meaningful analysis or debug for problem areas.
Describe the solution you would like
Request to enhance the custom instrumentation hook to capture all method input parameters as attributes. This will help us use span processors to rename spans appropriately as desired use case by use case
E.g. If custom instrumentation hook is enabled for Package.Method and Method takes 5 input params, make all 5 input params available as span attributes inp1=value1;inp2=value2;inp3=value3;inp4=value4;inp5=value5 and so on
Describe alternatives you have considered
We have captured the verbose log for Custom Instrumentation spans and noticed that we do not have any attributes captured today, so no meaningful data available to rename spans