Making logging to MongoDB the default

[Andrew Wilkins]

On Thu, Oct 22, 2015 at 5:39 PM roger peppe <roger.peppe at canonical.com>
wrote:

> This seems reasonable to me. For myself, the time I'm looking at
> all-machines.log
> is often when the system is broken. I wonder whether a reasonable
> substitute might be a low level tool that can operate directly on the mongo
> database to fetch the logs, bypassing the juju system.
>

+1
I'd like to see rsyslog gone, and the new logging to be enabled by default,
but I think we do need some tooling to extract logs when things go awry.


> I have one objection to the debug-log command - it doesn't
> appear to be possible to get the log up until the current time
> without blocking to wait for more messages when it gets
> to the end. So it's not quite a substitute because I can't easily
> grep the log without interrupting the grep command.
>
>   cheers,
>     rog.
>
> On 22 October 2015 at 09:51, Menno Smits <menno.smits at canonical.com>
> wrote:
> > I implemented the ability for Juju's logs to go to MongoDB some time ago.
> > This feature is available in 1.25 behind a feature flag and also gets
> > enabled automatically if the "jes" feature flag is enabled (logging via
> > rsyslog doesn't make much sense when using multiple environments in the
> one
> > system).
> >
> > There's also another separate feature flag which turns off rsyslog based
> > logging.
> >
> > The "jes" feature flag will be removed soon meaning that database logging
> > will need to become default functionality. The question is do we then
> also
> > remove logging to rsyslog functionality, or perhaps reverse the sense of
> the
> > rsyslog feature flag so that it's off by default but can be enabled if
> > people want it for some reason?
> >
> > I'm confident that the logging to the database feature is solid. I spent
> of
> > lot of time confirming that performance wouldn't be an issue. The code is
> > well tested. Automatic log rotation is implemented.
> >
> > The main issue I can see is that once rsyslog based logging is turned
> off we
> > lose the all-machines.log file which some people and systems no doubt
> rely
> > on. The logs for an environment can of course still be retrieved using
> the
> > "juju debug-log" command.
> >
> > If we really want something like all-machines.log, it wouldn't be /too/
> hard
> > to implement a worker which generates an all-machines.log style file in
> > real-time from the database logs. All the pieces to implement that
> already
> > exist, but I really don't have the bandwidth this cycle to do the work.
> >
> > Thoughts?
> >
> > - Menno
> >
> >
> >
> >
> >
> > --
> > Juju-dev mailing list
> > Juju-dev at lists.ubuntu.com
> > Modify settings or unsubscribe at:
> > https://lists.ubuntu.com/mailman/listinfo/juju-dev
> >
>
> --
> Juju-dev mailing list
> Juju-dev at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20151022/cf0264d6/attachment.html>