k3s/pkg/client/cache
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
..
doc.go finish testing client/cache 2014-08-04 14:50:01 -07:00
fifo.go Fix cache to use the "List then Watch" pattern. 2014-09-16 16:17:15 -07:00
fifo_test.go Fix cache to use the "List then Watch" pattern. 2014-09-16 16:17:15 -07:00
poller.go Add poller to cache. 2014-08-20 15:32:49 -07:00
poller_test.go Add poller to cache. 2014-08-20 15:32:49 -07:00
reflector.go Introduce some default log verbosity control 2014-09-25 16:30:14 -04:00
reflector_test.go Treat super short watches with no items received the same as watches that error immediately 2014-09-19 18:09:40 -07:00
store.go Fix cache to use the "List then Watch" pattern. 2014-09-16 16:17:15 -07:00
store_test.go Fix cache to use the "List then Watch" pattern. 2014-09-16 16:17:15 -07:00