Re: [libvirt] [PATCH 0/9] Use the systemd journal for logging
On Thu, Sep 27, 2012 at 11:44 AM, Daniel P. Berrange
<berrange(a)redhat.com> wrote:
The systemd journal provides a highly efficient way for apps
to generate structured log messages. Since systemd will be
used by default on future Fedora/RHEL distros (and likely
many others), we should take advantage of the journal out of
the box for improved logging capabilities.
Amongst other things, this allows very easy browsing of the
libvirt logs after the fact, filtering on filename / line
number / function name and more. This is a big benefit
to debugging, compared to current case where we need to
decide the filters when starting libvirtd. For example
it becomes possible to configure libvirt to include all
QEMU logging, and then later ask the journal for only
messages related to the QEMU json monitor.
--
Someone else posted a patchset for structured logging via lumberjack
which would support systemd as well as the other syslog daemons in an
abstract way without directly tying the project to systemd?
That seems like a better option IMHO. So I would vote for a NACK for the series.
https://www.redhat.com/archives/libvir-list/2012-September/msg01485.html
--
Doug Goldstein