On 4/15/15, 12:43 AM, "David Lang" <da...@lang.hm> wrote: >look at liblogging, it was started as part of lumberjack for exactly this >purpose.
liblogging does not currently support structured logging. I've opened an issue in GitHub to track that: https://github.com/rsyslog/liblogging/issues/22 On 4/15/15, 12:43 AM, "David Lang" <da...@lang.hm> wrote: >As far the idea of getting everyone to log in one format > >it's a nice dream, but there's no chance of getting everyone to use the >same >library > >It would be good to get a replacement for the systemd sd_journal_send() >call >that would send structured data to syslog, so that any apps that get >modified to >do something special for systemd can have that work leveraged to work >better >even without it. liblogging talks about a 'journalemu' mode, but the code isn't in the repository. I agree it's more likely that people will use the journal api than something new that gets proposed. If we want something ubiquitous, it needs to be easy to use/program to. And ideally it would ship by default from the distros or be a trivial library that can be pulled into a project. The journal API, despite its Linux-only nature, seems to have the most popularity (after the venerable syslog(3), of course). ~Matt --- Matt Ezell HPC Systems Administrator Oak Ridge National Laboratory _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
