Skip to content
This repository has been archived by the owner on Feb 9, 2022. It is now read-only.

Audit glog logging levels, make them consistent, and document our policy. #986

Open
ZackButcher opened this issue Aug 2, 2017 · 1 comment
Assignees
Milestone

Comments

@ZackButcher
Copy link
Contributor

We have a variety of glog logging levels throughout the Mixer codebase. Generally, glog.V(2) is what we consider default logging level, and glog.V(4) is what we consider verbose. However, some portions of the codebase use glog.V(3), some some use glog.V(9). It's likely that even more levels are used.

We need to audit our glog calls to determine where we log what information and at what verbosity. After that we should decide on a standard to follow throughout the codebase. Then we need to go update logging everywhere to conform to that standard.

@geeknoid
Copy link
Contributor

Part of the solution for this is #1489

@geeknoid geeknoid assigned geeknoid and unassigned ZackButcher Oct 26, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants