-
Notifications
You must be signed in to change notification settings - Fork 26
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
Expose config for collecting cgroup and kubelet metrics in kepler exporter API #202
Comments
Could you clarify more about this issue? Do you mean to expose it via the Kepler command arguments not via the config map? |
i mean expose it in
these values will be used to populate the kepler configmap |
Thank you. The key of the configmap variables are all listed here: https://github.com/sustainable-computing-io/kepler/blob/02c16c1e223e32b1d1f20f3c7ad8e8959eb2fd87/pkg/config/config.go#L77. |
@vimalk78 How about something like this. This allows us to add additional fields to each of the metric later on. E.g. say in future, cgroup can not only be enabled but also a filter can be applied on the metrics, this would allow for change to be exporter:
metrics: # keep all metrics under MetricSpec
cgroups: # feature specific config
enabled: true
kubelet:
enabled: true
foobar:
enabled: true
additional: config In general, I am wary of boolean flags. |
In addition to Currently, it uses the same config key though... |
enable/dsiable collecting cgroup and kubelet metrics by exposing bool config params in Exporter API.
Ref: https://github.com/sustainable-computing-io/kepler/pull/876/files
sustainable-computing-io/kepler#901
The text was updated successfully, but these errors were encountered: