Many thanks for the suggestions! I would like to point out that enabling selective debug is already possible since version 8.29 by using the parameters debug.file and debug.whitelist. You can find the documentation regarding those parameters at
http://www.rsyslog.com/doc/v8-stable/rainerscript/global.html I plan on summarizing the feedback in a short article in the closer future, but would still be glad about additional feedback. Jan 2017-08-22 10:20 GMT+02:00 mostolog--- via rsyslog <rsyslog@lists.adiscon.com>: > My 2 cents: > > As Rsyslog is used to handle several log formats, and encourage to use them, > it would be great it also use a well-known format. > Adding timestamps, caller (which component produces the log), thread-id or > an identifier to "trace" an event going from input to output (print message > id) would be great. > > Perhaps I would test a depth value instead of a loglevel. Enabling selective > debug (specific modules only) would also be great. > > Regards. > > > > On 14/08/17 10:59, Jan Gerhards wrote: >> >> 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. > > > _______________________________________________ > 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. _______________________________________________ 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.
