[systemd-devel] Logging in an enterprise environment

Lennart Poettering lennart at poettering.net
Wed Dec 11 06:21:21 PST 2013


On Wed, 11.12.13 14:25, Cecil Westerhof (Cecil.Westerhof at Snow.nl) wrote:

> >Journald's primary job is local logging, for complex logging setups we
> >recommend installing a logging services like rsyslog.
> 
> Would you not loose some of the advantages of journald this way? I
> understand that with using imjournal in rsyslog this probably could
> mostly be circumvented.

Well, you cannot look at the logs with journalctl if you do this, but
you cannot have it all..

> By the way: is just copying possible? What if an event is logged at
> the moment the copy is done?

That's fine. The journal parser is designed to handle half written files
as good as it can.

> >Eventually journald should provide you with both a pull and a push
> >model, however it currently onyl supports a pull model. Note that for
> 
> Where can I information about that, or do you mean copying the files?

By pull model I was referring to the GET HTTP command to the journal
gateway or copying via rsync/scp/....

Lennart

-- 
Lennart Poettering, Red Hat


More information about the systemd-devel mailing list