Default user feedback
William Reade
william.reade at canonical.com
Tue Apr 2 18:49:59 UTC 2013
On Tue, 2013-04-02 at 12:00 -0300, Gustavo Niemeyer wrote:
> I would cut this:
>
> 2013/04/02 13:04:22 INFO JUJU:juju:sync-tools cmd/juju: listing
> the source bucket
>
> Down to this:
>
> 2013/04/02 13:04:22 INFO listing the source bucket
I think there are two distinct issues here. First off, on reflection, I
don't think we should need to put the package prefix on log messages in
"main" packages at all; all that does is clutter things up. But I don't
think we should change the general policy of including package context
in other log messages.
I do agree more fully, I think, that the JUJU:etc badge is redundant.
ISTM that in a CLI context the user knows perfectly well what command
she typed, and in an agent context the log is named locally, and
aggregated elsewhere with a suitable badge. Can anyone point out what
I'm missing here?
> Which is exactly the information you suggested we tell the user about
> in the paste, plus the standard fields required for logging. That's
> enough for a user, and a developer can easily grep the source to find
> this message.
Package context is IME very helpful when reading logs; it's really nice
to be able to get a rough picture of what components are in play
*without* having to stop and grep the source all the time.
> I'd do that sooner rather than later, so we have a better user
> experience in 13.04. Doing this shouldn't be more than an afternoon of
> work for a single developer.
If we can get agreement on a small and clearly addressable tweak here, I
will put it on a card in the backlog and we'll be able to prioritize it
in context; if cost:benefit is good enough it'll get done. However, I'm
reluctant to commit to a timeframe; it's got some pretty healthy
competition re 13.04 priorities.
Cheers
William
More information about the Juju-dev
mailing list