On Tue, Oct 09, 2012 at 06:53:36AM -0400, Miloslav Trmac wrote:
----- Original Message -----
> Given systemd's fast adoption across a wide range of Linux distros,
> in particular the enterprise distros from Red Hat & SUSE, we're
> going to have journald support in places where structured logging
> really matters, likely expanding to all Linux distros in a reasonably
> short period. As such I don't really have a desire to also support
> Lumberjack format in libvirt natively. IMHO, system services should
> just log to journald and either journald can forward plain messages
> to syslog, or a tool can be created which pulls structured log data
> out of the journal and formats it in Lumberjack format.
I can live with that; however the libvirt use case I am looking at does
require adding more metadata fields, and I can't see how doing that
without memory allocation or imposing arbitrary limits is possible.
Imposing arbitrary limits it is, I guess.
I do have some ideas of adding more metadata too. What sort of pieces
of info are you looking for ? Based on your previous patches, I am
assuming the various virError struct fields at the very least ? Any
others ?
I think arbitrary limits will be ok, since while the number of metadata
fields is theoretically unlimited, in practice I don't see us needing
more than say 15 fields.
Regards,
Daniel
--
|:
http://berrange.com -o-
http://www.flickr.com/photos/dberrange/ :|
|:
http://libvirt.org -o-
http://virt-manager.org :|
|:
http://autobuild.org -o-
http://search.cpan.org/~danberr/ :|
|:
http://entangle-photo.org -o-
http://live.gnome.org/gtk-vnc :|