On Thu, Dec 11, 2014 at 01:56:24PM +0000, Holger Winkelmann [TP] wrote: > Hi, > > >> >However there is a need to forward log messages to remote syslog. > >> >We try to avoid to introduce a full blown syslog solution > >> >like i.e. rsyslog to just forward log messages to a remote syslog server. > > What Jóhann describes should work, even though it is a bit hacky. > > There is also a TODO item to add the functionality to send syslog packets > > over the network to either systemd-journald or a different tool. > > As we have worked on a ZeroMQ Journal gateway [1], which is a bit more > advanced > like the HTTP gateway and allows to "query" the journal apart of just > forwarding, > we could imagine to contribute to this work. As well of i.e. adding native > GELF [2] > forwarding to a Graylog2 server. > > Are there any plans to follow? I.e, having all protocols in a generic gateway, > or having one gateways per protocol? How the should we define which field > form the journal should be forwarded to syslog? IIUC, Lennart wanted to add this funcitonality to systemd-journal-upload or a new tool. I think it might be nicer to add it directly to systemd-journald, even though it would then use the network. The details are fuzzy atm.
Initial plan was to implement the most straighforward syslog forwarding, so only the MESSAGE field would be sent. I think that additional forwarders (e.g. GELF) should stay as separate projects. Zbyszek _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
