On Mar 21, 2019, at 8:27 AM, Itamar Turner-Trauring <itamar@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.