-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Metrics Deduplication #34141
Labels
enhancement
New feature or request
processor/metricstransform
Metrics Transform processor
waiting-for-code-owners
Comments
nicolastakashi
added
enhancement
New feature or request
needs triage
New item requiring triage
labels
Jul 17, 2024
github-actions
bot
added
the
processor/metricstransform
Metrics Transform processor
label
Jul 17, 2024
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This was referenced Jul 30, 2024
This was referenced Aug 13, 2024
This was referenced Aug 27, 2024
Hey @dmitryax did you had the opportunity to check this issue? |
This was referenced Sep 24, 2024
atoulme
added
waiting-for-code-owners
and removed
needs triage
New item requiring triage
labels
Oct 12, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
enhancement
New feature or request
processor/metricstransform
Metrics Transform processor
waiting-for-code-owners
Component(s)
processor/metricstransform
Is your feature request related to a problem? Please describe.
Previously, I created an issue (#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
The text was updated successfully, but these errors were encountered: