-
Notifications
You must be signed in to change notification settings - Fork 169
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
Consistent Log Levelling #1469
Labels
Comments
PalmPalm7
added a commit
to PalmPalm7/kepler
that referenced
this issue
Jun 20, 2024
Made changes to exisisting codebase with structured logs from format logs. [Github issue ref](sustainable-computing-io#1469). Added logging kepler with klog section on dev/README.md, [see here](https://github.com/sustainable-computing-io/kepler/blob/main/doc/dev/README.md).
PalmPalm7
added a commit
to PalmPalm7/kepler
that referenced
this issue
Jun 20, 2024
Made changes to exisisting codebase with structured logs from format logs. [Github issue ref](sustainable-computing-io#1469). Added logging kepler with klog section on dev/README.md, [see here](https://github.com/sustainable-computing-io/kepler/blob/main/doc/dev/README.md).
PalmPalm7
added a commit
to PalmPalm7/kepler
that referenced
this issue
Jun 20, 2024
Made changes to exisisting codebase with structured logs from format logs. [Github issue ref](sustainable-computing-io#1469). Added logging kepler with klog section on dev/README.md, [see here](https://github.com/sustainable-computing-io/kepler/blob/main/doc/dev/README.md). Signed-off-by: Andy Xie <anxie@redhat.com>
Link to PR: #1490. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
InfoS
instead ofInfoF
-v
flag to adjust the log verbosityWhy is this needed?
To make it easier for users and developers of Kepler to understand what's happening!
The text was updated successfully, but these errors were encountered: