Re: [Twisted-Python] Log output formatting (was Re: logging question)
I am happy with the information I get out of the logging system and the formatting of errors and tracebacks. We've recently come across two things that could be handled nicer however. 1) we use multiple logfiles. one for *all* messages, and another for *special* messages. It would be nice if the concept of multiple logfiles and the routing of messages to files was part of the system. 2) the above, coupled with the use of twisd and starting the logfiles was a little weird. Our main logfile is attached to the application like this application.setComponent(ILogObserver, FileLogObserver(logfile).emit) and the other logfile just starts on its own. I had expected to attach both of them to the application and set up an event filter for each. It's a little non-symmetric the way it is. -T
On Dec 1, 2011, at 12:32 PM, Tom Sheffler wrote:
1) we use multiple logfiles. one for *all* messages, and another for *special* messages. It would be nice if the concept of multiple logfiles and the routing of messages to files was part of the system.
You could implement this by having a single log observer which delegated to multiple other observers, possibly with filters. Sounds like a nice, simple, self-contained task that you could submit a patch for, if you wanted to get it into Twisted :). Please feel free to open a ticket with a patch. -glyph
On Dec 1, 2011, at 12:32 PM, Tom Sheffler wrote:
1) we use multiple logfiles. one for *all* messages, and another for *special* messages. It would be nice if the concept of multiple logfiles and the routing of messages to files was part of the system.
You could implement this by having a single log observer which delegated to multiple other observers, possibly with filters. Sounds like a nice, simple, self-contained task that you could submit a patch for, if you wanted to get it into Twisted :). Please feel free to open a ticket with a patch. -glyph
participants (2)
-
Glyph -
Tom Sheffler