During today’s Collector SIG Meeting on 17/07/2024, I presented a proof of concept (POC) I built over the last few days, which is available at this link: https://github.com/nicolastakashi/metricsdedupprocessor. We discussed whether this functionality should be implemented as a new component or as an additional feature in the metrics transform processor.
This issue is to discuss whether this should be implemented as a new component, or to have it done as part of the existing metricstransform processor component, during the meeting most of the maintainers seems to prefer if possible add a new feature to an existing component rather than a new component, and I'd like to discuss more about this strategy.
Describe the solution you'd like
Have the ability to deduplicate metrics based on DataPoints Attributes
Component(s)
processor/metricstransform
Is your feature request related to a problem? Please describe.
Previously, I created an issue (https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/20921) proposing a new component to deduplicate metrics before they are remotely written to a data store.
During today’s Collector SIG Meeting on 17/07/2024, I presented a proof of concept (POC) I built over the last few days, which is available at this link: https://github.com/nicolastakashi/metricsdedupprocessor. We discussed whether this functionality should be implemented as a new component or as an additional feature in the metrics transform processor.
This issue is to discuss whether this should be implemented as a new component, or to have it done as part of the existing metricstransform processor component, during the meeting most of the maintainers seems to prefer if possible add a new feature to an existing component rather than a new component, and I'd like to discuss more about this strategy.
Describe the solution you'd like
Have the ability to deduplicate metrics based on DataPoints Attributes
Describe alternatives you've considered
N/A
Additional context
N/A