Skip to content

[FEATURE] Add config flag to disable metric name processing #1676

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

Open
1 task done
prakashnathjha opened this issue Apr 26, 2025 · 0 comments
Open
1 task done

[FEATURE] Add config flag to disable metric name processing #1676

prakashnathjha opened this issue Apr 26, 2025 · 0 comments
Labels
enhancement New feature or request

Comments

@prakashnathjha
Copy link

prakashnathjha commented Apr 26, 2025

Is there an existing issue for this?

  • I have searched the existing issues

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

yace --raw-metric-names

Anything else?

No response

@prakashnathjha prakashnathjha added the enhancement New feature or request label Apr 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant