Making logging to MongoDB the default

[Marco Ceppi]

How do current customers, like dtag, who are very keen on having everything
goto syslog/rsyslog, going to keep that functionality going forward? Is
there an easy mechanism to get the logs out of mongodb?

All too often when I'm rummaging around in debug-hooks, I'll tail
/var/log/juju/unit-*.log to get an idea of what to expect or see what
failed. Does that workflow change with this feature?

Marco

On Thu, Oct 22, 2015, 6:04 AM Adam Collard <adam.collard at canonical.com>
wrote:

> On Thu, 22 Oct 2015 at 10:39 roger peppe <roger.peppe at canonical.com>
> wrote:
>
>> 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.
>>
>
> FWIW this is
> https://bugs.launchpad.net/juju-core/+bug/1390585
>
> --
> 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/a716b29d/attachment.html>