You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the current implementation of YACE it is processing the metric name it gets from AWS CloudWatch, basically converting it from CamelCase to snake_case. YACE does provides a flag to turn off this processing for metric labels, but not for metric name.
I would like to propose to add another flag that turns off metric name processing as well and use it exactly as AWS sends. The reason for this enhancement is that we ingest metric directly from AWS CW to our metric backend via CW Metric Stream in some of our environments and there we get the metric names as is in AWS but when we scrape it from YACE it changes the metric name and hence we don't have consistent metric names across envs which is a pain to maintain.
I can work on the implementation part of it as well if we agree that this can be part of the YACE configuration. Let me know your opinions. In case there are corner cases which I am not considering then please let me know.
Thanks!
What might the configuration look like?
We can have a flag like this or something better
yace --raw-metric-names
Anything else?
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Feature description
In the current implementation of YACE it is processing the metric name it gets from AWS CloudWatch, basically converting it from CamelCase to snake_case. YACE does provides a flag to turn off this processing for metric labels, but not for metric name.
I would like to propose to add another flag that turns off metric name processing as well and use it exactly as AWS sends. The reason for this enhancement is that we ingest metric directly from AWS CW to our metric backend via CW Metric Stream in some of our environments and there we get the metric names as is in AWS but when we scrape it from YACE it changes the metric name and hence we don't have consistent metric names across envs which is a pain to maintain.
I can work on the implementation part of it as well if we agree that this can be part of the YACE configuration. Let me know your opinions. In case there are corner cases which I am not considering then please let me know.
Thanks!
What might the configuration look like?
We can have a flag like this or something better
Anything else?
No response
The text was updated successfully, but these errors were encountered: