Clayton Coleman 4e56dafecc Introduce some default log verbosity control ... Move a lot of common error logging into better buckets: glog.Errorf() - Always an error glog.Warningf() - Something unexpected, but probably not an error glog.V(0) - Generally useful for this to ALWAYS be visible to an operator * Programmer errors * Logging extra info about a panic * CLI argument handling glog.V(1) - A reasonable default log level if you don't want verbosity * Information about config (listening on X, watching Y) * Errors that repeat frequently that relate to conditions that can be corrected (pod detected as unhealthy) glog.V(2) - Useful steady state information about the service * Logging HTTP requests and their exit code * System state changing (killing pod) * Controller state change events (starting pods) * Scheduler log messages glog.V(3) - Extended information about changes * More info about system state changes glog.V(4) - Debug level verbosity (for now) * Logging in particularly thorny parts of code where you may want to come back later and check it		2014-09-25 16:30:14 -04:00
..
api.go	Introduce some default log verbosity control	2014-09-25 16:30:14 -04:00
api_test.go	Services and Endpoints weren't properly sync'ing	2014-09-03 16:04:55 -04:00
config.go	Introduce some default log verbosity control	2014-09-25 16:30:14 -04:00
config_test.go	All types stored in etcd are now API objects.	2014-07-28 11:27:36 -07:00
doc.go	Address package level comments for readability.	2014-06-12 20:26:12 -07:00
etcd.go	Introduce some default log verbosity control	2014-09-25 16:30:14 -04:00
file.go	Introduce some default log verbosity control	2014-09-25 16:30:14 -04:00