errors are not aggregated into OOPS reports
Bug #809136 reported by
Robert Collins
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| txlongpoll |
Triaged
|
High
|
Unassigned | ||
Bug Description
This bug covers a multitude of issues:
For longpoll its a twisted service - we have an oops integration
module for twisted services in the LP tree: that needs to be broken
out (which is nontrivial, it needs about 3 packages factored out of LP
proper.). you could put it into wsgi-oops, but that project is a bit
awful to work with; I'd suggest the following package names:
txoops - tx specific glue
oopsclient - the oops gathering and writing code
lazr.oops or zopeoops - the zope oops glue (or leave this in the LP
tree for now)
| Changed in lazr.amqp: | |
| status: | New → Triaged |
| importance: | Undecided → High |
Revision history for this message
| Julian Edwards (julian-edwards) wrote | #1 |
Revision history for this message
| Julian Edwards (julian-edwards) wrote | #2 |
| Changed in txlongpoll: | |
| assignee: | nobody → Julian Edwards (julian-edwards) |
| Changed in txlongpoll: | |
| assignee: | Julian Edwards (julian-edwards) → nobody |
To post a comment you must log in.
The plan:
1. Create a python-oops-twisted project that will provide an API to attach an oops-generating log file observer.
2. The logpoll server needs to grow --oops-root and --oops-prefix command line options to set up a DateDirRepo.
3. Use the API from #1 in the longpoll server.
4. Make python-oops-twisted a dependency of txlongpoll