Bugzilla – Bug 6233
Minimal server logging
Last modified: 2011-11-06 23:22:52 UTC
I think it's a good compromise to set all logging level to ERROR, exept for one concern. I think there should be some logging of very basic events such as server startup and shutdown, and perhaps the launching and completion of library scans. I tried setting the 'server' logging to both INFO and WARN levels. WARN gives no startup information, and INFO is pretty chatty. Can a couple of very basic always-on log messages be added? Maybe something like: [10:03:47.9281] main::init (108) SqueezeCenter starting up... [10:03:52.5547] main::init (216) SqueezeCenter startup completed [12:15:09.4662] xxxxx::xxxxxx (451) Library scan initiated... [12:33:28.9438] xxxxx::xxxxxx (451) Library scan finished [15:22:57.0242] main::init (293) SqueezeCenter shutting down
Jim: are there specific logged items you want changed? Or just different log levels?
Neither, really, unless they're are already being logged, but I don't see them due to my level settings. I think that a handful of additional higher level events should always be logged. Very basic stuff: Server startup. Server shutdown. Scan of type xxx launched. Perhaps within the 'server' logging category or create a new category.
The vast majority of users don't care about the log file, I disagree that we need any logging by default, other than errors.
Ok, how about this? _I_ want to see when the server has started and when the server has shut down, because if you're going to fire up a log in the first place, you want to see when it starts and finishes logging.
The whole point of logging is to help diagnose problems that happen after the fact. Basic system startup and ending messages seem reasonable defaults. Then any warnings or error logs of out-of-the-ordinary behavior are on top of that.
how about a few simple yet obviously non-fatal $log->fatal messages on init and sigterm. This way, they show up at default levels, but users who want nothing can still set logger('server') to 'off' to get rid of them.
(In reply to comment #6) > how about a few simple yet obviously non-fatal $log->fatal messages on init and > sigterm. This way, they show up at default levels, but users who want nothing > can still set logger('server') to 'off' to get rid of them. That's what I was thinking - that you'd need to make them $log->fatal messages. I'm unfamiliar with how you can turn off all logging, though, unless you're talking about modifying the prefs file manually.
Unassigned bugs cannot have a priority.