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

Offer to move serializers and deserializers used across components of the contrib repo to codecs #21152

Closed
5 tasks
atoulme opened this issue Apr 24, 2023 · 3 comments

Comments

@atoulme
Copy link
Contributor

atoulme commented Apr 24, 2023

Component(s)

No response

Describe the issue you're reporting

This idea is originally from @MovieStoreGuy discussed during an APAC SIG meeting.

We are seeing a proliferation of encodings in this repository. The Kafka exporter is particularly popular right now with multiple new contributions offering to add support for various encodings.

It might make sense to move all those codecs to a library that is shared across components to reduce the burden of maintaining the same serialization code across multiple components. It would also allow any component to tap into the existing codecs.

The following codecs can be extracted from the code:

@atoulme atoulme added needs triage New item requiring triage and removed needs triage New item requiring triage labels Apr 24, 2023
@cparkins
Copy link
Contributor

@atoulme - I've done some preliminary work to move the Azure Resource Logs format into a shared directory for use between Kafka and Event Hubs. I'll try to get it rebased and create a preliminary PR of my work soon.

@github-actions
Copy link
Contributor

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 @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

@github-actions github-actions bot added the Stale label Jul 26, 2023
@github-actions
Copy link
Contributor

This issue has been closed as inactive because it has been stale for 120 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants