kubernetes
/
community
mirror of https://github.com/kubernetes/community.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #2887 from seunghunee/myfeature 

Add Trace level logging
This commit is contained in:
k8s-ci-robot 2018-11-02 10:16:34 -07:00 committed by GitHub
parent dd16f753ce a8cdc22956
commit 76fd89e0e1
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
contributors/devel/logging.md
View File

@ -23,8 +23,11 @@ The following conventions for the glog levels to use.
* Scheduler log messages * Scheduler log messages
* glog.V(3) - Extended information about changes * glog.V(3) - Extended information about changes
* More info about system state 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 * 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 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 environments may wish to run at V(3) or V(4). If you wish to change the log