Logging changes coming with juju 1.15

[Tim Penhey]

On 27/09/13 10:26, Kapil Thangavelu wrote:
> I don't think the log collection is the issue though this is still
> useful to help mitigate perhaps some of the log accumulation on disk
> (despite rotation archival). The problem is the primitive log display
> which amounts to tail aggregated syslog. As an end user, i don't care
> about framework internals, i care about seeing the provider mutations
> (create, destroy, sec group maybe), hook execution, and errors. With
> juju-core there isn't any ability to filter the log from the client on a
> given channel/hierarchy or level, and currently any usage of log
> basically fills up with ping api traffic obscuring actual content.

I agree entirely.  Although I feel that this is a step in the right
direction.

What we could do, and I was thinking about this after I wrote the last,
is to have the hook logs, and the hook log command, go through a
particular module, and make sure that is always logged out.

Ideally I want a different channel of information for user information,
as opposed to developer information.  This is still work in thought (not
even progress yet).

Tim