> On Oct 8, 2015, at 5:47 PM, exar...@twistedmatrix.com wrote: > > On 8 Oct, 11:38 pm, gl...@twistedmatrix.com wrote: >>> On Oct 8, 2015, at 6:04 AM, Itamar Turner-Trauring <ita...@itamarst.org> >>> wrote: >>> >>> Eliot 0.9 is out, with a new utility for pretty-printing log messages and >>> native journald support >>> <http://eliot.readthedocs.org/en/0.9.0/journald.html>. You can now route >>> Eliot logs to journald and when an error occurs easily find all logged >>> actions that led up to that particular error, as opposed to most logging >>> systems where this would involve reading all the logs and figuring out >>> which ones apply and which to ignore. >>> >>> Most logging systems can tell you what happened; Eliot tells you why it >>> happened: >> >> Cool, this looks awesome Itamar, thanks for letting us know! >> >> Does Eliot make use of the new logging system at all? If not, is there >> anything that might make Eliot's Twisted backend easier to maintain if we >> added it? Just kind of curious about adoption of those new APIs in the >> world of logging... > > As a user of Eliot and Twisted, an unpleasantness I commonly encounter is > that the logs written by trial when running tests for code that uses Eliot > for logging are a mish-mash of text messages and mangled Eliot logs. The > Eliot bits often get in the way of me reading the text part and the text > parts and mangling ensure I can't use any Eliot tools to interpret the Eliot > bits. > > My understanding is that there aren't any existing hooks in Twisted to > customize trial's logging which would allow this to be improved. > > There is some related discussion (maybe more oriented towards a particular > solution than a full description of the problem, though) on a ticket soon to > be a couple years old: > > https://twistedmatrix.com/trac/ticket/6939 > <https://twistedmatrix.com/trac/ticket/6939>
I actually ran into a variant of this exact same issue recently; thank you for directing my attention to this ticket. I agree that the log output should be customizable, but I'm curious: if the logs were just serialized as JSON by default everywhere, would that make it easier to make the Eliot tooling work well? -glyph
_______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
