-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[pkg/ottl] Add Base64Decode Converter #31543
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
**Description:** Adds a new `Base64Decode` function to facilitate ingest of base64 encoded data **Link to tracking Issue:** open-telemetry#31543 **Testing:** Added unit test **Documentation:** Updated the func readme.
Seems reasonable to me, and so would the inverse. We typically stick with specific functions, so I am ok with a specific |
**Description:** Adds a new `Base64Decode` function to facilitate ingest of base64 encoded data **Link to tracking Issue:** open-telemetry#31543 **Testing:** Added unit test **Documentation:** Updated the func readme.
…r Base64Decode
Closing as resolved via #31730. If you'd like to also add an encoding function, please feel free to reopen this issue or create another issue to track it. |
Component(s)
pkg/ottl
Is your feature request related to a problem? Please describe.
OTTL has no way to convert a base64 encoded string to plaintext, preventing the import of logs where the vendor encodes strings
Describe the solution you'd like
Add a new Converter, Base64Decode, that accepts a base64 encoded string and returns the decoded string.
Describe alternatives you've considered
Intermediary software to process inbound logs and decode base64 strings before passing to opentelemetry collector
Additional context
I am currently running a local fork with my implementation of a base64 decode function, I will create a branch and link it here.
The text was updated successfully, but these errors were encountered: