2017-08-12 23:39 GMT+02:00 Joe Blow via rsyslog <rsyslog@lists.adiscon.com>: > Is the output already in JSON? If not it'd be great to have something that > you could index and query directly.
Right now the output isn't in JSON. It is only accessible in the debug-log and only if debugging is enabled. However, I'm unsure about the benefits of having it in JSON format, since the messages themselves have no structure. The only index-able parts would be the (relative) timestamp, the thread and the file in which the output is generated. Because of this, I don't see many uses for debug-output in JSON, especially taking into consideration that the most important parts are the message itself. However, I would also be interested in hearing your opinion about the possible cases where JSON could be used. Jan > > Cheers, > > JB > > On Fri, Aug 11, 2017 at 9:13 AM, Jan Gerhards <jgerha...@adiscon.com> wrote: > >> Hi all, >> >> I am working on a refactoring of the debug output generated by rsyslog >> to increase usability not only for developers, but also for end users. >> >> For more information see >> https://www.linkedin.com/pulse/improving-rsyslog-debug- >> output-jan-gerhards >> >> As of rsyslog version 8.29 I have started by implementing first >> configuration options. As mentioned in the article, I would also be >> glad to hear from you about your ideas. >> >> Jan _______________________________________________ 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.
