summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorseunghunee <s-shin@bx.jp.nec.com>2018-11-02 04:59:08 +0000
committerseunghunee <s-shin@bx.jp.nec.com>2018-11-02 04:59:08 +0000
commita8cdc22956f5a961cd0bab4f89950fe79e243eba (patch)
tree484c95c9f746064adf2f0c9198bae52043d2907d
parent5a78c6867b9b40bc0ddfc1e6b23d78a84a2f6f57 (diff)
Add Trace level logging
Add Trace level logging to Logging Conventions
-rw-r--r--contributors/devel/logging.md5
1 files changed, 4 insertions, 1 deletions
diff --git a/contributors/devel/logging.md b/contributors/devel/logging.md
index 12a719de..889518a6 100644
--- a/contributors/devel/logging.md
+++ b/contributors/devel/logging.md
@@ -23,8 +23,11 @@ The following conventions for the glog levels to use.
* Scheduler log messages
* glog.V(3) - Extended information about changes
* More info about system state changes
- * glog.V(4) - Debug level verbosity (for now)
+ * glog.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
+ * Context to understand the steps leading up to errors and warnings
+ * More information for troubleshooting reported issues
As per the comments, the practical default level is V(2). Developers and QE
environments may wish to run at V(3) or V(4). If you wish to change the log