FS#32181 - [systemd] systemd-journal-gatewayd not built. Missing depends libmicrohttpd.

Attached to Project: Arch Linux
Opened by Massimiliano Torromeo (mtorromeo) - Tuesday, 23 October 2012, 12:38 GMT
Last edited by Dave Reisner (falconindy) - Thursday, 22 November 2012, 17:00 GMT
Task Type Feature Request
Category Packages: Core
Status Closed
Assigned To Dave Reisner (falconindy)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Since version 193 [1] systemd optionally provides a new service systemd-journal-gatewayd which provides a gateway to access the journal from http [2].

Arch does not ship this service since the PKGBUILD is missing a (optional?) dependency on libmicrohttpd. This would probably mean that we have to pull libmicrohttpd in [core].

If systemd is compiled with libmicrohttpd, the following additional files will be present in the final package:

/usr/lib/systemd/systemd-journal-gatewayd
/usr/lib/systemd/system/systemd-journal-gatewayd.service
/usr/lib/systemd/system/systemd-journal-gatewayd.socket
/usr/share/systemd/gatewayd/browse.html

The next version of systemd (195) improves the functionalities of gatewayd making it more useful and it would be nice if we shipped it by default.

Thanks.

[1] http://lists.freedesktop.org/archives/systemd-devel/2012-September/006738.html
[2] http://0pointer.de/public/journal-gatewayd
This task depends upon

Closed by  Dave Reisner (falconindy)
Thursday, 22 November 2012, 17:00 GMT
Reason for closing:  Implemented
Additional comments about closing:  systemd-196-2
Comment by Massimiliano Torromeo (mtorromeo) - Tuesday, 23 October 2012, 12:40 GMT
We could probably split gatewayd in a separate package to avoid making libmicrohttpd a hard dependency on systemd if this is an issue
Comment by Dave Reisner (falconindy) - Tuesday, 23 October 2012, 14:20 GMT
I'm not really interested in adding this. The gateway is of minimal value. "Nice to have" does not justify the added cost of maintaining libmicrohttpd in core.
Comment by Massimiliano Torromeo (mtorromeo) - Tuesday, 23 October 2012, 14:23 GMT
I was planning to use this to fetch and aggregate the log from multiple machines, which would be very useful to me and not just "nice to have" but of course I know this is not a common scenario.

Would it be acceptable to provide a [community] package built from systemd with just the gatewayd files?
Comment by Dave Reisner (falconindy) - Thursday, 25 October 2012, 02:15 GMT
The command line interface to the journal is far better than what gatewayd offers. Not only is it more flexible/featureful, I find it far more pleasant to use. What exactly is offered by gatewayd that's lacking in journalctl?
Comment by Massimiliano Torromeo (mtorromeo) - Thursday, 25 October 2012, 10:11 GMT
gatewayd offers an easy way to access the logs remotely over http and supports server-sent-events which allows for (web) applications to monitor and aggregate logs from multiple machines in real time.

What I find useful is not the web-interface provided by the service (browse.html) but the web-api to get the logs in json format over http.

If not for gatewayd, one would have to configure direct access to each machine, develop an in-house gateway or configure syslog to send logs over the network to a remote service.

Loading...