Robert Greig wrote:
1) the broker's default output logging level is nothing. If you start
it up, it gives no indication that it is doing anything at all. Is
this deliberate? I think it should really be INFO level, or at least
some level that enables the user to see that it is listening on a port
without running netstat.
I agree that it would be nice to get a bit more information on startup.
The current default log level is set to error+ as info and warning were
felt to be too verbose. To date the approach to adding log statements
has been rather ad-hoc and really needs to be codified into a more
explicit and useful system.
At present for example a warning is logged for every published message
that cannot be routed; every 'local' message dropped due to a 'no-local'
directive results in an info level log message etc. As these are
per-message events they could result in lots of log entries.
We could alter those events to be logged only at the debug level, but
they then become hard to see without further filtering as the output at
debug level is extremely verbose. The logging system does allow control
of levels by components but as it stands this does require a fair bit of
knowledge of the codebase.
I don't have any clear answers yet but I do think we need to start
thinking about more user friendly logging. Anyone else have any thoughts
here?
