-
Notifications
You must be signed in to change notification settings - Fork 97
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
[Feature Contribution]: Export carbon intensity to Prometheus #400
Comments
An interesting aspect here is to have a container, that is in a "tools" folder, which runs in the kubernetes cluster, so people can just grab it, and it emits prometheus events, and is configured with the location of the CA SDK as environment parameters (or whatever) to the container. Promeetheus emitter pod (maybe as a daemon) --> CA SDK in a pod--> <data souce i.e. ElectricityMaps/WattTime>
|
Blocked until #404 is done (.NET 8.0) |
This issue has not had any activity in 120 days. Please review this issue and ensure it is still relevant. If no more activity is detected on this issue for the next 20 days, it will be closed automatically. |
This issue has not had any activity for too long. If you believe this issue has been closed in error, please contact an administrator to re-open, or if absolutly relevant and necessary, create a new issue referencing this one. |
What happened?
Carbon Aware SDK can provide carbon intensity data. When the data are used combined with electricity consumption of the nodes that software are running on, the carbon emission can be calculated. This can be helpful for users to building and operating carbon-aware software.
Regarding the electricity consumption, there are several means to monitor with Prometheus. (e.g. node-exporter, redfish-exporter, kepler.) So it is convenient that also Carbon Aware SDK exports carbon intensity to Prometheus. It will be enable uses to monitoring the carbon emissions of software with the popular tools.
Code of Conduct
Feature Commitment
The text was updated successfully, but these errors were encountered: