Consistent Log Levelling

sustainable-computing-io / kepler

Kepler (Kubernetes-based Efficient Power Level Exporter) uses eBPF to probe performance counters and other system stats, use ML models to estimate workload energy consumption based on these stats, and exports them as Prometheus metrics

Apache License 2.0

1.09k stars 174 forks source link

What would you like to be added?

We should follow some of the guidelines in place here and overhaul our logging: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-instrumentation/logging.md

TL;DR

Prefer structured logging InfoS instead of InfoF
Use log levels 0 (default) -> 5 as documented in the guidelines above
Provide some documentation around the use of the -v flag to adjust the log verbosity

Why is this needed?

To make it easier for users and developers of Kepler to understand what's happening!

sustainable-computing-io / kepler

Consistent Log Levelling #1469

What would you like to be added?

Why is this needed?