No way of tracing/debugging http traffic content in the appserver.
Bug #1215750 reported by
Julian Edwards
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
High
|
Julian Edwards | ||
Bug Description
It would be very useful to have a config setting to enable various levels of http tracing in the appserver log.
Basic tracing would include request/response headers. Full tracing would include message content too.
The setting should be configurable "on the fly" to turn on and off tracing on request, ideally in the UI and API.
Related branches
lp://qastaging/~julian-edwards/maas/debug-middleware
- Gavin Panella (community): Approve
-
Diff: 202 lines (+91/-4)5 files modifiedsrc/maas/settings.py (+1/-0)
src/maasserver/__init__.py (+6/-0)
src/maasserver/middleware.py (+18/-2)
src/maasserver/models/config.py (+3/-0)
src/maasserver/tests/test_middleware.py (+63/-2)
| Changed in maas: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| tags: | added: log papercut |
| Changed in maas: | |
| milestone: | none → 13.10 |
| assignee: | nobody → Julian Edwards (julian-edwards) |
| status: | Triaged → In Progress |
| Changed in maas: | |
| status: | In Progress → Fix Committed |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
