-
Notifications
You must be signed in to change notification settings - Fork 49
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
List all consumed and generated metrics by opencost #138
Comments
I'm going to move this over to github.com/opencost/opencost-website/ since I think it would be useful over in the Documentation. |
Kubecost has https://docs.kubecost.com/architecture/user-metrics, which should be a good start (and might be identical). |
Really we need to revisit https://www.opencost.io/docs/integrations/opencost-exporter#available-prometheus-metrics and clean it up authoritatively. |
I really want to contribute, but I don't have enough Golang development knowledge to fetch relevant information from the codebase. |
Thanks for your attention @mattray
This page doesn't clarify which ones are consumed, and which ones are generated. Not only on opencost, but also on other parts like KSM.
Also, there is another list of metrics here: https://www.opencost.io/docs/integrations/prometheus#available-metrics |
I deployed a separate Prometheus for opencost and scraped my own infrastructure with existing cAdvisor, KSM, and node-exporter, and want to drop all other metrics that are not used on opencost and have no need for them.
I tried to dig into the code, but it's not a proper approach.
The missing part which I opened an issue for is the lack of a clean and exact list of consumed and generated metrics by opencost in docs, neither on kubecost nor on opencost.
I checked the exposed metrics and queried metrics by opencost, and they showed more and different metrics than docs.
Suggestion:
Provide a clean list for generated and consumed metrics in the docs, or place it on a separate file on the repo, to keep users stack updated with it.
The text was updated successfully, but these errors were encountered: