-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Add OTel-Arrow exporter/receiver to the testbed #33531
Comments
Pinging code owners for exporter/otelarrow: @jmacd @moh-osman3 @codeboten. See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Pinging code owners for receiver/otelarrow: @jmacd @moh-osman3. See Adding Labels via Comments if you do not have permissions to add labels yourself. |
1 similar comment
Pinging code owners for receiver/otelarrow: @jmacd @moh-osman3. See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Pinging code owners for exporter/otelarrow: @jmacd @moh-osman3 @codeboten. See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been closed as inactive because it has been stale for 120 days with no activity. |
Component(s)
exporter/otelarrow, receiver/otelarrow
Is your feature request related to a problem? Please describe.
It would be helpful to add OTel-Arrow exporter and receiver to the testbed.
Describe the solution you'd like
The testbed will have sender/receiver adapters added for these components.
Describe alternatives you've considered
This was prototyped: #16835
Additional context
This will be possible after #33518.
The text was updated successfully, but these errors were encountered: