-
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
[receiver/googlecloudpubsub] Add support for Encoding Extensions #37109
Labels
Comments
alexvanboxel
added
enhancement
New feature or request
needs triage
New item requiring triage
labels
Jan 9, 2025
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
@alexvanboxel Thanks for opening this request! Would you also contribute a PR for this? |
alexvanboxel
added a commit
to alexvanboxel/opentelemetry-collector-contrib
that referenced
this issue
Jan 10, 2025
…n-telemetry#37109) Added support for encoding extensions. Setting the encoding field in the config now references the extension. If it didn't find the extension it will fall back to searching the internal encoders. To make the build in encoders consistent with the extensions they now have the same interface. The README is adapted accordingly.
alexvanboxel
added a commit
to alexvanboxel/opentelemetry-collector-contrib
that referenced
this issue
Jan 10, 2025
…n-telemetry#37109) Added support for encoding extensions. Setting the encoding field in the config now references the extension. If it didn't find the extension it will fall back to searching the internal encoders. To make the build in encoders consistent with the extensions they now have the same interface. The README is adapted accordingly.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Component(s)
receiver/googlecloudpubsub
Is your feature request related to a problem? Please describe.
The receiver currently supports some build in encodings. The goal is to separate the encodings out of the receiver and put them in their own extension. Before this can happen, the receiver needs to support Encoding Extensions.
Describe the solution you'd like
Reuse the
encoding
field in the configuration file to select the Encoding Extensions. If non is defined, fall back to the build in encoders.Describe alternatives you've considered
No response
Additional context
After this change, the
cloud_logging
encoding will be extracted from the receiver.The text was updated successfully, but these errors were encountered: