Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move shared component map out of internal package #10036

Open
spiffyy99 opened this issue Apr 26, 2024 · 0 comments
Open

Move shared component map out of internal package #10036

spiffyy99 opened this issue Apr 26, 2024 · 0 comments

Comments

@spiffyy99
Copy link

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant