Opened 19 years ago

Last modified 6 years ago

#75 enhancement new

Switch http logging to twisted.logger

Reported by: itamarst Owned by:
Priority: normal Milestone:
Component: web Keywords: logging
Cc: spiv, itamarst, jknight, hypatia, jack Branch:


Change History (11)

comment:1 Changed 19 years ago by itamarst

Currently http uses its own, semi-broken hard-coded system.

The new system would generate log events, and then an
observer would log them, or create performance metrics
(publishable via resource?) and so on. A basic requirement
is to be able to have different log files for different
virtual hosts, in standard httpd format. Possibly this
should be extended to per-vhost logging of general messages
and errors.

comment:2 Changed 19 years ago by Glyph

your semi-brokenness :)

comment:3 Changed 18 years ago by itamarst

Out to be done as part of refactor. In return I am willing to write docs for
logging if you assign an issue about it to me.

comment:4 Changed 18 years ago by jknight

If someone tells me how to do this I may do it. Otherwise, itamar, perhaps you can do it for the new-
web branch?

comment:5 Changed 13 years ago by jack

Some potential improvements to what's there are in filed as #3757, #3758, #3759, #3760.

comment:6 Changed 13 years ago by jack

Cc: jack added

comment:7 Changed 12 years ago by Jean-Paul Calderone

Okay, so what does this really mean?

Right now, you can tell a site to write its CLF data to a particular file. If you don't, then something pretty gross happens involving twisted.python.log.logfile (but it could very easily just be log.msg instead).

This means you can have two sites, with two different CLF files. Or you can have one with a CLF file and the other going to the main log.

If you did everything via the logging system, how would you handle these cases?

comment:8 Changed 11 years ago by <automation>

Owner: jknight deleted

comment:9 Changed 7 years ago by Wilfredo Sánchez Vega

Keywords: logging added

comment:10 Changed 6 years ago by Wilfredo Sánchez Vega <wsanchez@…>

In c1bc604:

Error: Processor CommitTicketReference failed
 does not appear to be a Git repository. See the log for more information.

comment:11 Changed 6 years ago by Aaron Maxwell

Summary: Switch http logging to new logging infrastructureSwitch http logging to twisted.logger
Note: See TracTickets for help on using tickets.