cmdline: support debug-log

[Mark Ramm]

Users need some way to see what's happening in the cloud without sshing to individual machines.

No infrastructure is in place to support this story; it'll need handling in state and on the API server. Past discussions have indicated that a target for juju-core/log, that also pushes data to a mongodb capped collection, may be a sensible way forward.

[Dimiter Naydenov (dimitern)]

I believe Ian is working on this already.

[William Reade (fwereade)]

This is already released, but has some limitations, captured in lp:1190950 and lp:1190953.

[Kurt (burnbrighter)]

This is not fixed in version 1.12. juju debug-log is not working. I see no output from the log. I am also deploying consolidated services on some single nodes.

[Dave Cheney (dave-cheney)]

I'm chasing the exact point 1.12 was branched and checking if the fix
was merged after that point.

Regardless of that, we won't be backporting this fix to the 1.12
branch. The next stable release, 1.14 will include this fix (and
others to debug-log).

On Fri, Aug 30, 2013 at 10:48 AM, Kurt <email address hidden> wrote:
> This is not fixed in version 1.12. juju debug-log is not working. I
> see no output from the log. I am also deploying consolidated services
> on some single nodes.
>
> --
> You received this bug notification because you are subscribed to juju-
> core.
> Matching subscriptions: MOAR JUJU SPAM!
> https://bugs.launchpad.net/bugs/1027877
>
> Title:
> cmdline: support debug-log
>
> Status in juju-core:
> Fix Released
>
> Bug description:
> Users need some way to see what's happening in the cloud without
> sshing to individual machines.
>
> No infrastructure is in place to support this story; it'll need
> handling in state and on the API server. Past discussions have
> indicated that a target for juju-core/log, that also pushes data to a
> mongodb capped collection, may be a sensible way forward.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju-core/+bug/1027877/+subscriptions