More on logging changes in Juju 1.26.0

[Wayne Witzel]

I have some naive questions.

    * We are still writing logs to the local disk, we are just no longer
using rsyslog to stream / aggregate them?
    * Is there a separate mongo instance that handles the log collection?

On Mon, Nov 9, 2015 at 11:32 PM, Tim Penhey <tim.penhey at canonical.com>
wrote:

> On 10/11/15 17:30, Stuart Bishop wrote:
> > On 9 November 2015 at 11:34, Menno Smits <menno.smits at canonical.com>
> wrote:
> >
> >> In a recent thread I highlighted the upcoming change in Juju's logging
> where
> >> logs from machine and unit agents will be streamed over Juju's API
> instead
> >> of via rsyslogd. Two things came out of that discussion:
> >>
> >> 1. a desire for juju debug-logs to support a "non-tailing" mode (as per
> bug
> >> 1390585)
> >> 2. a desire for a tool to dump the logs out of the database in the case
> of
> >> Juju being unavailable for some reason.
> >
> >
> >> As always, questions and comments welcome.
> >
> > will 'juju debug-log' and 'juju dump-logs' support the common --format
> > argument or similar, allowing me to spit out the structured data? I'm
> > mainly interested in spitting out a stream of JSON dictionaries to
> > pass to filters and formatters.
> >
>
> debug-log will (RSN™) but it doesn't yet
>
> juju-dumplogs is a server side log recovery tool, and not for general use.
>
> Tim.
>
> --
> Juju-dev mailing list
> Juju-dev at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>



-- 
Wayne Witzel III
wayne.witzel at canonical.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20151116/e943abb6/attachment.html>