Merge pull request #12 from liranp/master
Fix misspellings in README
Tim Hockin authored 3 years ago
GitHub committed 3 years ago
| 75 | 75 | **V-levels give operators an easy way to control the chattiness of log |
| 76 | 76 | operations**. V-levels provide a way for a given package to distinguish |
| 77 | 77 | the relative importance or verbosity of a given log message. Then, if |
| 78 | a particular logger or package is is logging too many messages, the user | |
| 79 | of the package can simply chang the v-levels for that library. | |
| 78 | a particular logger or package is logging too many messages, the user | |
| 79 | of the package can simply change the v-levels for that library. | |
| 80 | 80 | |
| 81 | 81 | ## Why not more named levels, like Warning? |
| 82 | 82 | |
| 139 | 139 | Kubernetes codebase): |
| 140 | 140 | |
| 141 | 141 | - `klog.V(4).Infof("Client is returning errors: code %v, error %v", |
| 142 | responseCode, err)` becomes `logger.V(4).Error(error, "client returned an | |
| 142 | responseCode, err)` becomes `logger.Error(err, "client returned an | |
| 143 | 143 | error", "code", responseCode)` |
| 144 | 144 | |
| 145 | 145 | - `klog.V(4).Infof("Got a Retry-After %ds response for attempt %d to %v", |