I'm all for taking rsyslog out of the equation even on linux... what's nice about it is that, because we'd be writing log output separately to both the remote syslog and to the local file log, we wouldn't need to worry about log rotation of the local log screwing up what gets sent to the remote syslog. It's trivial to have loggo write to two or more targets (the file plus one for each state server).
On Fri, Aug 8, 2014 at 8:58 AM, Gabriel Samfira < gsamf...@cloudbasesolutions.com> wrote: > The standard Go syslog package works great (with slight changes). As a > bonus, it would be great to remove the dependency on rsyslog from all > non bootstrap nodes if all we need it to do is tail the juju log and > send it to an agregator :). > > As a native windows alternative, If we really do need to log to > something else then a file on a windows machine, we may as well go with > the built in event log. > > Gabriel > > On 08.08.2014 12:41, jaquilina wrote: > > there is an rsyslog for windows but obviously it requires a license > > > > http://www.rsyslog.com/windows-agent/ > > > > On 2014-08-06 16:42, Nate Finch wrote: > >> Fair enough, I forgot about debug-log. Do we have an idea of how > >> well aggregate logs from Windows machines? rsyslog wont run there. > >> We might be able to do a go-only solution by using the syslog > >> package.... gabriel made a port of it that will run on Windows and > >> supports TLS: https://github.com/gabriel-samfira/syslog [4] Then > >> wed just have to give loggo a writer that writes to both the log file > >> and syslog. > >> > >> On Wed, Aug 6, 2014 at 10:24 AM, John Meinel <j...@arbash-meinel.com > >> [5]> wrote: > >> > >>> all-machines.log is where we aggregate the messages from all > >>> machines/units/etc. > >>> It is likely to get big, which is why we want log rotate, but if you > >>> want to be able to "juju debug-log" and actually get the feed of > >>> everything that is going on, that needs to be *somewhere*. And yes, > >>> wed like to switch to something like log stash instead, but until we > >>> get there we do still need it. > >>> John > >>> =:-> > >>> > >>> On Wed, Aug 6, 2014 at 4:13 PM, Tim Penhey <tim.pen...@canonical.com > >>> [3]> wrote: > >>> > >>>> On 06/08/14 16:11, Nate Finch wrote: > >>>> > all-machines.log seems both redundant and a ticking time bomb > >>>> of disk > >>>> > space usage. Do we really need it? Can we drop it and maybe > >>>> later > >>>> > schedule some time to use something like logstash that is both > >>>> more > >>>> > featureful and is cross platform compatible (unlike rsyslog)? > >>>> > >>>> not yet... > >>>> > >>>> debug-log uses all-machines.log, we cannot get rid of it at this > >>>> stage. > >>>> > >>>> We cant drop it until a replacement is in place. > >>>> > >>>> Tim > >>>> > >>>> -- > >>>> Juju-dev mailing list > >>>> Juju-dev@lists.ubuntu.com [1] > >>>> Modify settings or unsubscribe at: > >>>> https://lists.ubuntu.com/mailman/listinfo/juju-dev [2] > >> > >> > >> > >> Links: > >> ------ > >> [1] mailto:Juju-dev@lists.ubuntu.com > >> [2] https://lists.ubuntu.com/mailman/listinfo/juju-dev > >> [3] mailto:tim.pen...@canonical.com > >> [4] https://github.com/gabriel-samfira/syslog > >> [5] mailto:j...@arbash-meinel.com > > > -- > Juju-dev mailing list > Juju-dev@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju-dev >
-- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
