On Fri, Oct 31, 2014 at 6:30 PM, Rich Freeman <[email protected]> wrote: > On Fri, Oct 31, 2014 at 6:09 PM, Tom H <[email protected]> wrote:
>> The systemd line was always that if you wanted to ship your logs off >> to another box, use rsyslog. So I've never understood the embedding of >> an httpd in systemd. I guess that the httpd server's useful if if you >> want a basic send-the-logs-to-another-box-as-is, but that, if you want >> to filter or manipulate the journald output, you have to use rsyslog >> or syslog-ng. > > If you're going to implement a log manager there is no reason to not > let it export logs to a central manager. True. On second thought, I now remember that Lennart said that there was no intention to use syslog's udptcp output. So he hadn't ruled out http. And I misrepresented the systemd line. > As far as filtering/manipulating logs goes, you can do plenty of that > with journalctl already, and it supports dumping your logs in json so > you can do anything you want with them in another tool. There aren't > really any such tools around yet, but I'm sure we'll see them come up. You can filter/manipulate logs with journalctl - and nicely so - but you can't combine it with journal-gatewayd; the latter exports all the logs, as shown in the output of "journalctl". Maybe there'll be one day a tool to tweak the output of journal-gatewayd...
