summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChristopher Hein <me@christopherhein.com>2018-12-06 03:00:17 +0000
committerChristopher Hein <me@christopherhein.com>2018-12-06 03:00:17 +0000
commit744d649e9ad9d5bb66b17fdac6840b328347fd92 (patch)
tree21b23015209e120694e3b39e4ab75b5feb52442c
parent77c7fa36f7950b8be0cc9c6a4bab53375f71e646 (diff)
Change devel guide glog references to klog
Signed-off-by: Christopher Hein <me@christopherhein.com>
-rw-r--r--contributors/devel/logging.md22
1 files changed, 11 insertions, 11 deletions
diff --git a/contributors/devel/logging.md b/contributors/devel/logging.md
index 889518a6..c4da6829 100644
--- a/contributors/devel/logging.md
+++ b/contributors/devel/logging.md
@@ -1,31 +1,31 @@
## Logging Conventions
-The following conventions for the glog levels to use.
-[glog](http://godoc.org/github.com/golang/glog) is globally preferred to
+The following conventions for the klog levels to use.
+[klog](http://godoc.org/github.com/kubernetes/klog) is globally preferred to
[log](http://golang.org/pkg/log/) for better runtime control.
-* glog.Errorf() - Always an error
+* klog.Errorf() - Always an error
-* glog.Warningf() - Something unexpected, but probably not an error
+* klog.Warningf() - Something unexpected, but probably not an error
-* glog.Infof() has multiple levels:
- * glog.V(0) - Generally useful for this to ALWAYS be visible to an operator
+* klog.Infof() has multiple levels:
+ * klog.V(0) - Generally useful for this to ALWAYS be visible to an operator
* Programmer errors
* Logging extra info about a panic
* CLI argument handling
- * glog.V(1) - A reasonable default log level if you don't want verbosity.
+ * klog.V(1) - A reasonable default log level if you don't want verbosity.
* Information about config (listening on X, watching Y)
* Errors that repeat frequently that relate to conditions that can be corrected (pod detected as unhealthy)
- * glog.V(2) - Useful steady state information about the service and important log messages that may correlate to significant changes in the system. This is the recommended default log level for most systems.
+ * klog.V(2) - Useful steady state information about the service and important log messages that may correlate to significant changes in the system. This is the recommended default log level for most systems.
* Logging HTTP requests and their exit code
* System state changing (killing pod)
* Controller state change events (starting pods)
* Scheduler log messages
- * glog.V(3) - Extended information about changes
+ * klog.V(3) - Extended information about changes
* More info about system state changes
- * glog.V(4) - Debug level verbosity
+ * klog.V(4) - Debug level verbosity
* Logging in particularly thorny parts of code where you may want to come back later and check it
- * glog.V(5) - Trace level verbosity
+ * klog.V(5) - Trace level verbosity
* Context to understand the steps leading up to errors and warnings
* More information for troubleshooting reported issues