Closed Bug 750248 Opened 12 years ago Closed 10 years ago

Use dictConfig logging configuration

Categories

(developer.mozilla.org Graveyard :: General, enhancement)

Product:
developer.mozilla.org Graveyard
Component:
General
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: jsocol, Unassigned)

Details

(Whiteboard: [dev-papercut]) 

We should get rid of log_settings and use the real/modern dictConfig logging configuration for Django[1]. That would make it much easier to set up Raven/Sentry[2] to handle logs as well as tracebacks.

[1] https://docs.djangoproject.com/en/1.4/topics/logging/#an-example
[2] http://raven.readthedocs.org/en/latest/config/django.html
Blocks: 750240
No longer depends on: 750240
Component: Website → Landing pages
No longer blocks: 750240
Blocks: 795356
No longer blocks: 795356
:groovecoder, is this still valid?
Severity: normal → enhancement
Component: Landing pages → General
Flags: needinfo?(lcrouch)
Whiteboard: [dev-papercut]
We have a config dictionary for logging. I can't see if we're using dictConfig specifically though. :ubernostrum ?
Flags: needinfo?(lcrouch) → needinfo?(jbennett)
Django's logging system converts what you put in settings.py into the appropriate dictConfig under the hood.
Flags: needinfo?(jbennett)
Whiteboard: [dev-papercut] → [dev-papercut][closeme?]
Ok, I'm going to close this as FIXED.  Please feel free to reopen it with more information if this request is still valid.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Whiteboard: [dev-papercut][closeme?] → [dev-papercut]
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.