Hey @peterbourgon and @dgryski, I'm curious to here both of your thoughts on "http://k8s.io/klog " i.e., would you recommend it?
Seems to address the major issues with "golang/glog", while keeping the nice features e.g., per-"module" verbosity levels
https://godoc.org/k8s.io/klog https://twitter.com/peterbourgon/status/972177627996831744 …
-
Personally, I prefer V to named levels. I find that I want several grades of verbosity, whether for debug, tracing, dumping clang equivs or other. It gives me more control. Yes it is arbitrary, but so is WARN vs ERROR. Each their own, but life scratches my itch for now.
(cc 
In my experience, code authors aren't great at judging info vs warning vs error, especially in libraries used in multiple contexts, and log spam is always a challenge. With realtime monitoring, alerting severity thresholds are defined by the operator, not by the code author
-
-
As an operator I wish I could turn on and off log levels at runtime without restart. Or even historically. If it weren’t for some logs being costly to produce (slower) I would be tempted to log everything and filter outside the binary, before emitting to the aggregator.
-
There was discussion about having controller-runtime copy what cockroachdb does - allow you to connect to an endpoint and tee logs at a level until you disconnect. Would like that everywhere (auth protected)
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.