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

Merge pull request #5188 from mickeypash/patch-1 

Mention the new structured logging convention
This commit is contained in:
Kubernetes Prow Robot 2020-10-08 09:36:38 -07:00 committed by GitHub
parent 1321e75723 4eeba4d57b
commit 01480706ed
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
contributors/devel/sig-instrumentation/logging.md
View File

@ -29,6 +29,8 @@ The following conventions for the klog levels to use.
* Context to understand the steps leading up to errors and warnings * Context to understand the steps leading up to errors and warnings
* More information for troubleshooting reported issues * More information for troubleshooting reported issues
* klog.InfoS() - structured logs to the INFO log
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
level, you can pass in `-v=X` where X is the desired maximum level to log. level, you can pass in `-v=X` where X is the desired maximum level to log.