Merge lp:~lifeless/python-oops-tools/timeline into lp:python-oops-tools
Proposed by
Robert Collins
Status: | Merged |
---|---|
Approved by: | Robert Collins |
Approved revision: | 46 |
Merged at revision: | 43 |
Proposed branch: | lp:~lifeless/python-oops-tools/timeline |
Merge into: | lp:python-oops-tools |
Diff against target: |
135 lines (+30/-3) 6 files modified
buildout-templates/bin/oopstools.wsgi.in (+14/-1) buildout-templates/src/oopstools/settings.py.in (+1/-0) buildout.cfg (+0/-1) setup.py (+4/-0) src/oopstools/NEWS.txt (+6/-0) versions.cfg (+5/-1) |
To merge this branch: | bzr merge lp:~lifeless/python-oops-tools/timeline |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
William Grant | code | Approve | |
Review via email:
|
Commit message
Django 1.3.3, new djangorecipe, and start capturing SQL activity in OOPSes raised by oops-tools itself.
Description of the change
Upgrade oops-tools infrastructure a bit, get latest django in the 1.3 series - 1.3.3, and then on top of that introduce timeline-django so we can capture the SQL calls being made when oops-tools itself has an issue.
This also provides a bit of a reference-use-case for using django-timeline.
We may find we need to implement tighter query filtering - I don't know whether the django-sso-auth stuff will be caught properly, so we may end up deploying, getting a couple of traces, and then disabling in prod.
To post a comment you must log in.
I'm a little reluctant to switch SQL logging on by default, but otherwise fine