Is your feature request related to a problem? Please describe.
Edge Processor team at Splunk would like to make use of this internal component https://github.com/open-telemetry/opentelemetry-collector/blob/main/internal/sharedcomponent/sharedcomponent.go. This will help us build a custom S2S receiver that supports both different data types (metrics and logs) in the same receiver. This is necessary because the receiver should be able to handle both data types on the same port, and only one receiver can spawn per port number.
Describe the solution you'd like
The shared component map should be moved out of the internal package and into a publicly accessible location.
Describe alternatives you've considered
Keeping a copy of the shared map or implementing it in our own codebase, however this creates unneeded engineering effort and maintenance.
Is your feature request related to a problem? Please describe. Edge Processor team at Splunk would like to make use of this internal component https://github.com/open-telemetry/opentelemetry-collector/blob/main/internal/sharedcomponent/sharedcomponent.go. This will help us build a custom S2S receiver that supports both different data types (metrics and logs) in the same receiver. This is necessary because the receiver should be able to handle both data types on the same port, and only one receiver can spawn per port number.
Describe the solution you'd like The shared component map should be moved out of the internal package and into a publicly accessible location.
Describe alternatives you've considered