[systemd-devel] remote journal enhancements

[Holger Winkelmann [TP]]

Hi all,

we are following the discussion initiated by Cecil about systemd
journal for a while. The last couple of weeks we have developed
a Erlang adapter for the journal to allow structured native logging.
Therefore we have developed a ejournald [1] backend for the Erlang
logging framework lager [2]. ejournald also got a Erlang wrapper
to query the journal for log entries and emit messages for new
arriving messages.

By writing distributed applications we will look further for log
aggregation in the style of the systems-journal-gateway.
Regarding this I would like to know about the idea and plans of
the systemd community. Following the emails about logger optimization
Lennart mentioned something about kdbus transports for logging (on
kdbus systems) further systemd has usually dubs APIs for introspection
but the journal is access directly by journalctl and the corresponding
C-API.

Are there any plans/ideas to give the journald a D-Bus/kdbus API for querying
the journal? Or should reading/querying the journal totally decoupled
from journald in a daemon like systems-journal-gateway?

If we work on a separate journal-gateway do you have any ideas/requirement
about the API this should expose, again like D-Bus for local communication
and i.e. HTTP, JSON-RPC, AMQP etc. for remote communication? Should we
include any access control which honors the underlying journal fils ACLs
or should we have ACLs for given fields on the journal?

BTW: we know about "use rsyslog" answer but this was not the option here,
wer looking for a lightweight gateway solutions like the gateway with some
extended functionality.

[1] @Mirjam, please provide the Repo at Github
[2] https://github.com/basho/lager



-- 
Holger Winkelmann
Travelping

email: hw at travelping.com
phone: +49-391-819099-223
mobil: +49-171-5594745
http://www.linkedin.com/in/hwinkel