> On Mar 21, 2019, at 8:27 AM, Itamar Turner-Trauring <ita...@itamarst.org>
> wrote:
>
> Python and Twisted's built-in logging output a stream of factoids: they’re
> interesting, but you can’t really tell what’s going on.
>
> Why is your application slow?
> What caused this code path to be chosen?
> Why did this error happen?
> Standard logging can’t answer these questions.
>
> But with a better model you could understand what and why things happened in
> your application. You could pinpoint performance bottlenecks, you could
> understand what happened when, who called what.
>
I should note that if anyone out there is interested in getting involved with
contributing to Twisted, but the bugs look big and daunting, finding a module
that uses twisted.python.log and updating it to:
1. use twisted.logger
2. format all of its fields with structured information rather than string
formatting
would really help with the consumption of Twisted's native log messages by more
advanced tools like Eliot, and generally make Twisted better and push it into
the future.
-glyph
_______________________________________________
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
https://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
