From 4eeba4d57bed01502cb09598a74d21671d4ee876 Mon Sep 17 00:00:00 2001 From: Mickey Pashov Date: Sat, 3 Oct 2020 20:08:21 +0100 Subject: Mention the new structured logging convention As part of the structured logging migration It's probably worth having a line here for `InfoS()` --- contributors/devel/sig-instrumentation/logging.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/contributors/devel/sig-instrumentation/logging.md b/contributors/devel/sig-instrumentation/logging.md index c4da6829..d7e052c0 100644 --- a/contributors/devel/sig-instrumentation/logging.md +++ b/contributors/devel/sig-instrumentation/logging.md @@ -29,6 +29,8 @@ The following conventions for the klog levels to use. * Context to understand the steps leading up to errors and warnings * 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 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. -- cgit v1.2.3