-
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
[processor/metricstransform] Include Splitby operation #16276
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
I think this should be implemented as new functionality in the transform processor instead of metricstransform processor. @TylerHelmuth do you have any ideas on how this can be done? |
I'm struggle to imaging what it's like to build a metric out of an attribute, but I'm sure the transform processor could be made to do it now. |
We are currently using the
|
Yes I think a function could be added to do that. It would probably be best to do it at the Metric context, but it's possible to do at the DataPoint Context. The caveat with doing it at the datapoint level is that you shouldn't remove items from the datapoint list. |
That is fair, it would help unblock our dependancy on signalfx exporter performing this operation. |
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 Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
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 Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been closed as inactive because it has been stale for 120 days with no activity. |
Component(s)
processor/metricstransform
Is your feature request related to a problem? Please describe.
In the components current form, it is not possible without some complicated aggregation logic to convert an attribute to a new metric.
Describe the solution you'd like
What I'd like to do is the following:
Describe alternatives you've considered
At this point in time, to make
split_metric
logic work, I have either done some combination of label aggregation or using thesignalfx exporter
to perform this operation.Additional context
While A solution exists and works, it is split across two components so keeping metric names consistent across different systems isn't possible.
The text was updated successfully, but these errors were encountered: